chore: add v3.0.0 schemas

[jonaslagoni]

Description
This PR adds the new schemas for v3.0.0 so we can start applying changes.

This PR also merges the changes from Master that have happened since the branch was created.

fixes #175

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[jonaslagoni]

Should this live on it's own branch instead of next-major 🤔

[magicmatatjahu]

@jonaslagoni I guess next-major refers to the next (major) version of AsyncAPI, right? If yes, then it's ok.

[jonaslagoni]

I will re-target this for next-spec-major once created, as that is where it will live until 3.0 is released.

[KhudaDad414]

@jonaslagoni I have been thinking about moving bindings schemas here and saw that this branch can be a good place to add them if we want to have bindings schemas for 3.0.0 of course. Are there any plans on merging this so I can open a PR for bindings?

[jonaslagoni]

@jonaslagoni I have been thinking about moving bindings schemas here and saw that this branch can be a good place to add them if we want to have bindings schemas for 3.0.0 of course. Are there any plans on merging this so I can open a PR for bindings?

Yep!

I will create the corresponding branches and changes Monday next week so we can start moving this along 🙂

[jonaslagoni]

Damn, when targeted branches are removed, remaining PRs are closed as well with no way to retarget them...

[derberg]

why would you remove next-major ?

[jonaslagoni]

@derberg bot did when I used /rtm

[jonaslagoni]

I cannot re-open my own PRs 🤨 Can you @derberg?

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[jonaslagoni]

Thats a lot of conflicts for something so easy as running a single command... Gonna remake it.