fix: validate dynamic reply channel addresses

[be-student]

Closes #876.

Adds a v3 core Spectral rule for dynamic reply addresses. When reply.address is present, the referenced channel must leave address null or undefined. The validator follows local component-reference chains and reports the error at the reply channel reference.

Validation:

• npm run lint
• npm run build:esm
• npm run test:unit -- --runInBand on Node 20: 2,446 tests passed

Implemented and tested with Codex.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5a88483

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.

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 passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud