Show resolved schema names for $dynamicRef-bound properties

[aqeelat]

Summary

Optional Swagger UI rendering enhancement for $dynamicRef-bound properties. This is a UX improvement that can be worked on in parallel and is not a prerequisite for resolver correctness.

Reference implementation / showcase

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

The showcase includes response schemas where a property such as data structurally renders as object, while a friendlier resolved schema name such as PaginatedPetItems may be useful to display.

Related issues

• Related coordination issue: Proposal: coordinate $dynamicRef support across ApiDOM, Swagger Client, and Swagger UI #10912
• User-facing $dynamicRef bug: Issue: $dynamicRef is not supported in Swagger UI / OpenAPI 3.1 #10651
• ApiDOM resolver work: Add $dynamicRef dereference support for OpenAPI 3.1 and 3.2 strategies apidom#5176
• Swagger Client resolver work: Support OpenAPI 3.1/3.2 $dynamicRef resolution with ApiDOM swagger-client#4223

Proposed scope

• Preserve structural type display such as object, array, or string.
• When metadata is available, also show a useful resolved schema/component name for $dynamicRef-bound properties.
• Example: render a response data property as PaginatedPetItems object, or an equivalent clear label, instead of only object.