fix(cli): fix AsyncAPI publish messages not generating send methods

[fern-support]

Description

Refs: Customer request from Immix

Link to Devin run: https://app.devin.ai/sessions/50ce682058004d24beb034e75ffe07d7
Requested by: @fern-support

Fixes an issue where AsyncAPI v2 publish operations (client-to-server messages) were not generating send methods in generated SDKs. The IR was only containing server-origin messages, causing websocket clients to be missing the ability to send subscription requests.

Changes Made

• Modified ChannelConverter2_X.convertMessage() to pass the payload directly to SchemaOrReferenceConverter instead of resolving it first
• Changed the condition from requiring schema != null to just checking if the converter output is non-null
• Uses schemaOrReferenceConverterOutput.type directly instead of creating a new TypeReference from the converted schema
• Removed unused TypeReference import
• Added versions.yml entry (v3.56.10)
• Updated AsyncAPI JSON refs test snapshots to reflect the fix

Root cause: When a message payload is a reference to an existing schema (e.g., $ref: "#/components/schemas/SubscribeRequest"), the SchemaOrReferenceConverter.maybeConvertReferenceObject returns output WITHOUT the schema property (only type and inlinedTypes). The original code required schema != null to proceed, which caused publish messages with schema references to be silently dropped.

Testing

• Snapshot tests updated (asyncapi-json-refs-fdr.snap, asyncapi-json-refs-ir.snap)
• Manual testing with Immix AsyncAPI spec

Human Review Checklist

1. Verify publish operations specifically: The updated snapshots show subscribe (server→client) messages now being generated. Please verify that publish (client→server) operations also work correctly with the Immix AsyncAPI spec.
2. Logic correctness: The converter's type property should be valid for both reference and inline schema cases
3. Both branches affected: The change to the oneOf branch (which also had the schema != null check) is intentional - both branches now use the same pattern

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring