feat: adapt Kafka bindings to v3

[lbroudoux]

Signed-off-by: Laurent Broudoux laurent.broudoux@gmail.com

Description

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

• Adapts README to explain with have different versions of bindings for v3 and v3,
• Add specific README to track v2 related changes and documentation,
• Add specific README to track v2 related changes and documentation.

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

Related issue(s)

Relates to #182

[dalelane]

spotted a few minor things we could fix, but overall this is exactly what we need

[lbroudoux]

All good: fix the typos and apply suggestions. Thanks @dalelane, for the review.

[derberg]

just make sure you target next-major-spec branch 🙏🏼 and then merge

[derberg]

oh that is intentional? but not much aligned with others, eventually master should contain latest and if you want maybe we can on release date create v2 tag here in this repo, so you can link to it?

cc @jonaslagoni

[smoya]

oh that is intentional? but not much aligned with others, eventually master should contain latest

Both solutions are good enough to me 🤔. @derberg's solution ends up looking cleaner for maintainers. @lbroudoux suggestion seems kinda clearer for users when reaching this repo. At least for now, not sure when more spec major versions start going out.

and if you want maybe we can on release date create v2 tag here in this repo, so you can link to it?

Additionally, we will need to change the links in v2 spec that point to this repo so they point to bindings compatible with spec v2, otherwise, people will reach bindings for spec v3 instead.
As a technical detail, we might wanna use a branch called v2 rather than a tag, so in case we need to release a fix for any binding for spec v2, we can do it in such branch and we won't need to retag.

The base branch was changed.

[lbroudoux]

Now replaced by #226.

Could you all confirm we can cancel this one?

[dalelane]

agreed