feat(pulsar): improve channel with pulsar bindings

[gulecroc]

Reason/Context

Operation only render the channel address, whereas in case of Pulsar it is the combination of :

• channel.bindings.pulsar.persistence
• server.bindings.pulsar.tenant
• channel.bindings.pulsar.namespace
• channel.address

Description

Could it be possible to reuse pulsar bindings to provide channel fullname ?

<persistence>://<tenant>/<namespace>/<address>

Thank you

[github-actions]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup 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.

[tarunspandit]

Hi maintainers — I would like to be considered for this issue under the 2026-08 Microgrant Program, if it remains available after the round is finalized.

I reviewed the issue and would approach it by:

1. adding a small, isolated formatter that derives the Pulsar channel full name from channel persistence, server tenant, channel namespace, and address;
2. defining safe fallbacks for partial or missing Pulsar bindings so existing documents do not regress;
3. applying the formatter only to the Pulsar display path, preserving current behavior for other protocols; and
4. adding focused tests for persistent/non-persistent topics, complete bindings, partial bindings, and non-Pulsar channels.

I understand assignment is at the maintainers' discretion, and I will wait for confirmation before opening a PR. Is this scope and approach acceptable?