OpenAPI 3.0: references defined in examples should not be dereferenced

When defining a reference inside of examples fields on various spec objects, instead of the Example Object, the reference should not be dereferenced.

For this specification:

  responses:
    ExampleResponse:
      description: An error occurred
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ExampleModel'
          examples:
            $ref: '#/components/examples/tshirt'
  examples:
    tshirt:
      summary: Sample T-shirt data
      value:
        # Example value starts here
        id: 17
        name: T-shirt
        description: 100% cotton shirt
        categories: [clothes]

when the example gets dereferenced, each field of tshirt will be seen as a separate example. Each of them will be rendered as an option for examples select:

This does not happen for OpenAPI 3.1:

Additional context or thoughts

To fix this, we need to utilise ApiDOM for OpenAPI 3.0.

Originally reported by @glowcloud

Start by reproducing the issue with the OpenAPI 3.0 YAML example in this report and compare it with the OpenAPI 3.1 behavior. Trace the OpenAPI 3.0 dereferencing path and investigate how ApiDOM can preserve the reference as one Example Object. Done means the referenced example renders as a single selectable example rather than separate fields.