@W-23748894 feat(webhooks): suppress Try-It per-operation for OAS 3.1/3.2 webhooks

[alexpmule]

@W-23748894

What

Renders OAS 3.1/3.2 top-level webhooks as first-class documentation.

Part of the webhooks feature for TD-0333486. Depends on @api-components/amf-helper-mixin >= 4.5.36 (PR W-23748894-webhooks on that repo), which resolves top-level apiContract#webhooks via an additive fallback.

Per-repo behavior:

• api-navigation — dedicated "Webhooks" nav section.
• api-method-documentation — shows the webhook event name instead of a URL.
• api-documentation — suppresses the per-operation Try-It for webhooks (webhooks are event-driven; there is nothing to invoke).

Why

Webhooks are top-level in OAS 3.1/3.2 (not under paths). AC4: webhooks must render as their own first-class section with Try-It suppressed.

Dependency / publish gate

Ship the mixin (4.5.36) first, then raise the peer floor to ^4.5.36 here. Below 4.5.36 the resolver fallback does not exist and the feature silently no-ops with no error/log/metric.

Tests

Green in chromium + firefox. Inline AMF expanded-model fixtures.

Known QA notes (P2, non-blocking, tracked for the PR discussion)

• AC-03 is proven in two halves (mixin suite proves resolution on 4.5.36 source; this suite proves suppression on the installed mixin) — no single end-to-end select→resolve→render→no-Try-It test, and no .action DOM-absence assertion.
• No test consumes the real generated model; a future generator change to the apiContract#webhooks predicate would pass GREEN and break prod. A smoke test against a real compact model (at least in nav) is recommended.

Scope

Draft for review.

[salesforce-cla]

Thanks for the contribution! Unfortunately we can't verify the commit author(s): Alex Perez <a***@s***.com>. One possible solution is to add that email to your GitHub account. Alternatively you can change your commits to another email and force push the change. After getting your commits associated with your GitHub account, refresh the status of this Pull Request.