feat: add all recommended and must supported schema formats

[jonaslagoni]

Description
This PR adds all the MUST and RECOMMENDED supported schema formats. This is to enable auto-completion more than anything because the underlying type is string, it's only to help know which known values are there.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[GreenRover]

If tooling will support proto but it is not listed here it is not a problem?

[jonaslagoni]

These are just all known schema formats listed in https://www.asyncapi.com/docs/reference/specification/v2.6.0#messageObjectSchemaFormatTable

We cannot add values we haven't agreed upon, you can of course still use custom ones.

Adding new keys for other schema formats is part of the spec discussion.

[derberg]

looks like manual stuff that will have to be updated with each release

not a problem, just mentioning because this requires updates in readme, and probably script that generates new version definitions?

[jonaslagoni]

not a problem, just mentioning because this requires updates in readme, and probably script that generates new version definitions?

I'll see if I can include it in the script, that would be easiest yea.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[jonaslagoni]

Alright, I made a few changes.

1. Adapted the create new version script:

• Before, we could accidentally replace versions that were unintended, i.e. it would happen in the next version (3.1.0) because it would replace the application/vnd.oai.openapi;version=3.0.0 to application/vnd.oai.openapi;version=3.1.0.
• If the new version is a major version change (i.e. first number is not equal to the latest), replace all AsyncAPI schema format entries with the new.
• If the new version is minor or fix, add a new entry of AsyncAPI schema format.

2. Adapted the root .asyncapi property to use const instead of enum. We will never have more then one value.
3. Removed all v2 schema formats

Depending on whether this or #370 is merged first, we need to adapt the function addNewSchemaVersion.

[jonaslagoni]

Applied your suggestions @fmvilas and applied the recent changes from master.

I adapted the add new version script so the validation of schema property is also changed accordingly with the right schema format values.

[jonaslagoni]

Please have another look @fmvilas @derberg 🙇

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[derberg]

LGTM 🚀

tested on local 👇🏼

[jonaslagoni]

@derberg did you test the auto-suggestion feature for schemaFormat values, not so much whether schema is validated? 😄

[derberg]

you mean this 👇

[jonaslagoni]

@derberg yeeep, perfect 👌

[jonaslagoni]

/rtm

[derberg]

@fmvilas is out on holidays next 4 weeks, and for not PR is blocked as he requested changes to it in the past.

I will use admin rights to dismiss his request for changes as we won't wait a month for him

[asyncapi-bot]

🎉 This PR is included in version 6.0.0-next-major-spec.5 🎉

The release is available on:

• npm package (@next-major-spec dist-tag)
• GitHub release

Your semantic-release bot 📦🚀