Remove Persistent Topics v3 API - use custom media type instead

[lhotari]

Fixes #14104

Motivation

• PR PIP 110: Support Topic metadata - PART-1 create topic with properties #12818 changes for PIP-110 broke the API. A newer admin client cannot be used with an older broker.
• It’s possible to have the current v2 API for creating persistent topics to handle multiple different payload types
  The challenge seems to be that in the old method, the number of partitions was passed in the payload as a single integer without having a JSON object at all. This makes it harder to extend the existing API, but doesn’t make it impossible.
• This solution is based on request’s “Content Type”
  Content-Type: application/vnd.partitioned-topic-metadata+json on request, @Consumes("application/vnd.partitioned-topic-metadata+json") on method that handles the new payload type.

Modifications

• use custom media type application/vnd.partitioned-topic-metadata+json to distinguish the new content payload type

[nicoloboschi]

LGTM

[eolivelli]

LGTM

but we should find a way to clearly document this in the documentation
maybe swagger is already well documenting this new media type?

could you please verify ?

[tisonkun]

but we should find a way to clearly document this in the documentation
maybe swagger is already well documenting this new media type?

@eolivelli Swagger distinguishes endpoints by verb + path only. It can be a docs issue, see also #18947.