fix(parser): trigger custom parsers on operation.channel.messages.*.payload

[q404365631]

What

Adds four new JSONPath entries to customSchemasPathsV3 so custom schema parsers
also fire on payloads/headers reached via operation.channel.messages (when the
channel is $ref'd to an external file).

Why

As reported in #1099, when an AsyncAPI 3.0 document defines an operation like:

operations:
  FooOperation:
    action: send
    channel:
      $ref: otherFile.yaml#/channels/BarChannel

... and the referenced channel defines a messages.AMessage.payload with a custom
schemaFormat, the custom parser is never invoked because
customSchemasPathsV3 did not include $.operations.*.channel.messages.*.payload
(it covered $.operations.*.messages.*.payload but not the channel. intermediate
level). The user-reported workaround (re-declaring the channel under root
channels:) confirmed the path mismatch.

Changes

packages/parser/src/custom-operations/parse-schema.ts: Added 4 paths to
customSchemasPathsV3:

• $.operations.*.channel.messages.*.payload
• $.operations.*.channel.messages.*.headers
• $.components.operations.*.channel.messages.*.payload
• $.components.operations.*.channel.messages.*.headers

Plus a changeset for @asyncapi/parser (patch).

2 files changed, 17 insertions(+).

Fixes #1099

[changeset-bot]

🦋 Changeset detected

Latest commit: a7d6da9

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@asyncapi/parser	Patch

Not sure what this means? Click here to learn what changesets are.

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

[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