Implement extended tests for bindings and AsyncAPI v3.0.0 definitions

[Pakisan]

Why do we need this improvement?

I have already wrote basic tests for bindings and AsyncAPI v3.0.0 definitions

Now, it's time to tune them up

I expect next:

• basic scenarios for schema:
  • empty
  • example
  • without required fields
  • only required fields
  • extended
  • wrongly extended
• basic scenarios for property:
  • string
  • object
  • null
  • number
  • boolean
  • array
• All current misses are described in related discussion - https://github.com/asyncapi/spec-json-schemas/discussions/546

Initial tests are here: https://github.com/asyncapi/spec-json-schemas/pull/540 Related issue, witch schemas new format: https://github.com/asyncapi/spec-json-schemas/pull/549

How will this change help?

We will be sure that after changes in our schemes nothing will be broken

Screenshots

No response

How could it be implemented/designed?

Tune up basic tests

🚧 Breaking changes

No

👀 Have you checked for similar open issues?

• [X] I checked and didn't find a similar issue

🏢 Have you read the Contributing Guidelines?

• [X] I have read the Contributing Guidelines

Are you willing to work on this issue?

Yes I am willing to submit a PR!