Ensure that 3.0.0 was implemented correctly

[Pakisan]

Check that I didn't lost any changes done, in specification schema, after 04.10.2023

Known open specifications to check compatibility with:

• [x] adeo-kafka-request-reply-asyncapi.yml
• [x] anyof-asyncapi.yml
• [x] application-headers-asyncapi.yml
• [x] correlation-id-asyncapi.yml
• [x] gitter-streaming-asyncapi.yml
• [x] kraken-websocket-request-reply-message-filter-in-reply-asyncapi.yml
• [x] kraken-websocket-request-reply-multiple-channels-asyncapi.yml
• [x] mercure-asyncapi.yml
• [x] not-asyncapi.yml
• [x] oneof-asyncapi.yml
• [x] operation-security-asyncapi.yml
• [x] rpc-client-asyncapi.yml
• [x] rpc-server-asyncapi.yml
• [x] simple-asyncapi.yml
• [x] slack-rtm-asyncapi.yml
• [x] streetlights-kafka-asyncapi.yml
• [x] streetlights-mqtt-asyncapi.yml
• [x] streetlights-operation-security-asyncapi.yml
• [x] websocket-gemini-asyncapi.yml

[Pakisan]

adeo-kafka-request-reply-asyncapi.yml is blocked by https://github.com/asyncapi/spec/issues/1031

[Pakisan]

Similar issues with Schema:

example usage instead of examples

• https://github.com/asyncapi/jasyncapi/issues/163

Unknown property nullable

• https://github.com/asyncapi/jasyncapi/issues/164