Support all custom validation for AsyncAPI 2.x.x

[magicmatatjahu]

Chore summary

This issue contains list of rules that we need introduce in the AsyncAPI ruleset to fullfil all custom validation for 2.x.x versions.

Note: This is a collective task, which serves for cooperation and informing the community what was done and what is left to do.

Note: You can also write your own proposals/features/PRs in the comments, I will update then the main list.

Tasks

• [AsyncAPI] Enhance parameters and variables linting #1102
  • feat(rulesets): add rules for validation of server variables and channel parameters #2101
• [AsyncAPI] Identify more orphaned components besides schemas #1103
• AsyncAPI rule to validate property example in schema #1732
• Add rule to check uniqueness of operationId #2102
  • feat(rulesets): add rule to check uniqueness operationId of AsyncAPI operations #2121
• Add rule to check uniqueness of tags.*.name #2103
  • feat(rulesets): add rules for validation uniqueness of tag names #2104
• Add a rule to validate security in the servers #2123
  • feat(rulesets): validate channel servers, server securities and operation securities #2122
• Add a rule to validate servers in the channel #2124
  • feat(rulesets): validate channel servers, server securities and operation securities #2122
• Add rule to check uniqueness of messageId #2223
  • feat(rulesets): check uniqueness of AsyncAPI messages #2224
• Add a rule to validate unresolved AsyncAPI document #2261
  • feat(rulesets): validate unresolved AsyncAPI document #2262
• feat(rulesets): add rule to check if messageId is defined #2281
• feat(rulesets): add rule to check if the AsyncAPI document is using the latest version #2282
• fix(rulesets): handle empty payload and headers in AsyncAPI message's examples validation #2284
• ...

Additional context

As the AsyncAPI team will take an active part in the development of the official ruleset for AsyncAPI we should support the validation of the overall specification.

[derberg]

we had a release where uniqueness of messageId was introduced