fix: parse payload and headers of messages defined in operation.channel with non-default parsers

[glowcloud]

Description
Fixes an issue where non-default parsers did not parse payload and headers schemas if the message containing them was defined only under operation.channel. This affected resolved definitions that inline resolved objects and caused the @asyncapi/react-component not to render these fields.

Before:

After:

Related issue(s)

Fixes #1099

[changeset-bot]

⚠️ No Changeset found

Latest commit: 239361c

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