Code samples ignore global security when multiple security schemes are defined (ApiKey + Bearer)

When using multiple security schemes (ApiKey + Bearer) defined globally in OpenAPI 3.0, the Try it out request correctly sends both headers, but the Code samples generated by Swagger UI include only one of them (typically the first one).

This is inconsistent with the OpenAPI spec and leads to misleading code samples.

To Reproduce

Use Swagger UI 5.22.0

Define global security in your OpenAPI spec with both ApiKey and BearerAuth:

openapi: 3.0.1
info:
  title: Test API
  version: 1.0.0

servers:
  - url: https://example.com/api

security:
  - ApiKeyAuth: []
    BearerAuth: []

components:
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: apiKey
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT

paths:
  /models:
    get:
      summary: List models
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                type: object

Open Swagger UI, authorize with both apiKey and Bearer token.
Click Try it out → Execute → curl request shows both headers correctly.
Check the Code samples section → curl / PHP / other languages

Expected behavior
The generated Code samples should include both headers, matching the executed request and the OpenAPI specification.

Start by reproducing the issue in Swagger UI 5.22.0 with the supplied OpenAPI document and compare the executed curl request with the generated curl, PHP, and other samples. Done means code samples include both the ApiKeyAuth and BearerAuth headers, matching the specification and Try it out request.