fix: add resolved-document validation rules for v3 channel/server references

[Shyam-Raghuwanshi]

Fixes #924

Desc

• Added new 'asyncapi3-required-operation-channel-unambiguity-resolved' rule
  that runs on the resolved document to verify operation channels exist
  in root channels by comparing object references
• Added new 'asyncapi3-required-channel-servers-unambiguity-resolved' rule
  that runs on the resolved document to verify channel servers exist
  in root servers by comparing object references

These new rules complement the existing unresolved rules to catch both:

1. Same-file invalid references (caught by pattern matching)
2. Cross-file invalid references (caught by object identity check)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 93270f8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[sonarqubecloud]

Quality Gate failed

Failed conditions
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE