Show resolved schema names for $dynamicRef-bound properties

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: swagger-api/swagger-ui#10912
• User-facing $dynamicRef bug: swagger-api/swagger-ui#10651
• ApiDOM resolver work: swagger-api/apidom#5176
• Swagger Client resolver work: swagger-api/swagger-js#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.

No file or test is named. Start with the linked adoption-tracker showcase and trace Swagger UI’s schema/property rendering path for $dynamicRef; done means preserving structural type labels while adding resolved names such as PaginatedPetItems when metadata is available.