fix: add asyncapi3-channel-parameters rule

[AugustusWayne]

Resolves #875

Description :

This PR addresses issue #875 by improving the handling of the asyncapi3-channel-parameters rule. The previous implementation had inconsistencies in how parameters were validated against AsyncAPI specifications, leading to potential misinterpretations or false positives.

Changes Introduced :

Enhanced validation logic to correctly verify channel parameters.
Fixed edge cases where valid parameters were incorrectly flagged as errors.
Improved error messages to provide more context for users.
Additional test cases were added to ensure robust rule enforcement.

[changeset-bot]

⚠️ No Changeset found

Latest commit: b86de54

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 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

[AugustusWayne]

@smoya @jonaslagoni @magicmatatjahu Can anyone please take a look at this pr? I'm happy to make any changes if necessary