feat: let channels be identified by ID. Address is now moved into a new field

[smoya]

This PR allows channels to be identified by an ID rather than by their address. Instead, the address has now been moved into a new field called address.

This is a breaking change so it should be considered as a candidate for v3.0.0.

Related issue(s):

See asyncapi/spec#663 for knowing about the reason behind this RFC.

CC @char0n @magicmatatjahu @derberg

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this pull request, add a comment with detailed explanation.

There can be many reasons why some specific pull request has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this pull request forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

[smoya]

@fmvilas @derberg would you mind removing the stale label?

[jonaslagoni]

@smoya if you switch branch you can convert this to the new definitions 🙂

[smoya]

@smoya if you switch branch you can convert this to the new definitions 🙂

Yeah, thanks. Now is done. The reality is that maintaining a change in a new JSON Schema file (3.0) for a long time (major version) is hard since other versions will happen in the meantime. Keeping the new schema up to date is a manual and hard task.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[smoya]

Closing in favour of #264