[#434] feat: added create topic endpoint

[ilkerkocatepe]

This PR resolves issue #434

[ilkerkocatepe]

Hi @ppatierno,
thank you for the review, I updated the files which you mentioned.

[ppatierno]

@ilkerkocatepe thanks for addressing my comments. I left two more and also I think you should rebase again because you are bringing some changes in the pom.xml which are not related to your PR but commits already merged into main.

[ppatierno]

@ilkerkocatepe thanks for addressing my comments but thinking more on your API proposal I have a more "destructive" one :-)
This proposal is about using the /admin/topics/{topicName} URL where you specify the topic name as part of the path and then passing replication factor and partitions via query parameters. While it would work, I think it's not that much extensible for future additions like allowing to specify topic configuration when creating a topic.
I think we should go in a different direction by using a JSON as body of the HTTP POST request where you can specify parameters. What I have in mind is something like this, let me know what you think ...

The URL would be just /admin/topics/ and the POST request could have a body like the following:

{
    "topic_name": "my-new-topic",
    "partitions_count": 5,
    "replication_factor": 3,
}

The above JSON would be extensible in the future, allowing to have a "configs" field for example with a properties map for topic configuration parameters.
Of course, it means changing the OpenAPI spec as well and providing examples of body within the spec as well.
I am really sorry to realize this later and that we were going in a wrong direction.
Wdyt?

[ilkerkocatepe]

You are absolutely right. Also, it will be proper way according to REST standards. I would like to edit implementation :)

[ppatierno]

@ilkerkocatepe great to hear that you are still onboard! My apologies for realising this so late. Thanks for the effort!

[ilkerkocatepe]

Hi again @ppatierno,
I committed issues that you mentioned,
but something happened weird when rebasing, I think due to use of IDE version controlling.

[scholzj]

Is it intentional that it contains the dpeendency changes etc.?

[ppatierno]

@ilkerkocatepe as Jakub said you have something which belongs to an already existing commit from here ea03491
Can you fix the PR please?

[ppatierno]

@ilkerkocatepe we are planning to start releasing bridge 0.31.0 RC1 by the end of the week and it would be great to have this in. Do you think you are able clean this PR (removing the unrelated commit) without opening a new one and copying over the code there? Otherwise I will just merge this .

[ilkerkocatepe]

I think I messed up everything and need help :/

[ppatierno]

@ilkerkocatepe I just merged it. Thanks!