Support OpenAPI 3.1/3.2 $dynamicRef resolution with ApiDOM

Summary

Proposed Swagger Client resolver work for OpenAPI 3.1/3.2 $dynamicRef schemas using ApiDOM. This issue is linked from the broader Swagger UI coordination issue so the prerequisite relationship is visible.

Reference implementation / showcase

• https://github.com/aqeelat/openapi-dynamicref-adoption-tracker/

The showcase repository includes OpenAPI examples used to validate that dynamic response envelopes and root-local #/components/... refs resolve as expected.

Related issues

• Related coordination issue: swagger-api/swagger-ui#10912
• Depends on ApiDOM core support: swagger-api/apidom#5176
• Related user-facing Swagger UI bug: swagger-api/swagger-ui#10651
• Related non-blocking Swagger UI display enhancement: swagger-api/swagger-ui#10913

Proposed scope

• Delegate schemas with $dynamicRef to ApiDOM's dereference logic.
• Resolve with full OpenAPI document context where dynamic scope requires root-level context.
• Preserve compatibility for root-local #/components/... refs inside schemas that also declare absolute $id values.
• Add regression coverage for a dynamic-ref response schema shape.

Start with the referenced ApiDOM core support issue #5176, then review the dynamic-ref examples in the adoption tracker and the existing Swagger Client resolver. Done means dynamicRef schemas resolve with full OpenAPI document context, root-local component refs remain compatible with absolute $id values, and regression coverage is added for the response schema shape.