feat: adapt Kafka bindings to v3

[lbroudoux]

Description

This is the companion PR to asyncapi/bindings#221.

As discussed and proposed here in issue #182, this PR:

• Duplicates previous version 0.4.0 in v2-0.4.0 and v3-0.4.0 to keep track of bindings changes related to AsyncAPI v3 or v3
• Schemas related to v2 are referencing the v2 specification extensions schema (https://raw.githubusercontent.com/asyncapi/spec-json-schemas/v2.14.0/schemas/2.4.0.json#/definitions/specificationExtension)
• Schemas related to v3 are referencing the v3 specification extension schema (http://asyncapi.com/definitions/3.0.0/specificationExtension.json)

Another PR with specific schemas for v2 and v3 is on its way on asyncapi/spec-json-schemas.

Related issue(s)

Relates to asyncapi/bindings#182

[jonaslagoni]

@lbroudoux you need to re-target the PR to next-major-spec 🙂

[lbroudoux]

Oops...

[jonaslagoni]

In order for the bindings to be validated as well, you need to adapt:

spec-json-schemas/definitions/3.0.0/channelBindingsObject.json

Line 84 in 9639ca9

"kafka": {

As well for message, operation and server 🙂

[lbroudoux]

Tests are failing but seem normal as http://asyncapi.com/bindings/kafka/v3-0.4.0/server.json is not yet deployed and available.

[dalelane]

thanks for doing this!

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[lbroudoux]

Now replaced by #453

Could you all confirm we can cancel this one?

[dalelane]

Now replaced by #453

Could you all confirm we can cancel this one?

yeh, makes sense to me