fix: ignore rendering responses with extensions in the schema

[DarkMatter-999]

Description

This PR fixes a rendering bug in the Responses when using custom OpenAPI extensions (x-*) inside the responses object.

Motivation and Context

fixes #10561
Swagger UI previously attempted to render all entries in the responses object, including custom extensions like x-tenant as actual HTTP responses.

How Has This Been Tested?

Manually tested with an OpenAPI 3.1.0 spec containing x-tenant under responses
Verified that the Responses section renders correctly and without errors
Confirmed that valid responses (200, 500, etc.) still display as expected
Ran relevant tests, no regressions observed.

Environment:
OS: Linux
Browser: Chromium 139
Swagger UI: master Branch

Schema used for testing:

{
  "openapi" : "3.1.0",
  "paths" : {
    "/hello" : {
      "get" : {
        "responses" : {
          "200" : {
            "description" : "The hello message",
            "content" : {
              "text/plain" : {
                "schema" : {
                  "type" : "string"
                }
              }
            },
            "x-tenant" : "acme"
          },
          "500" : {
            "description" : "Internal server error",
            "x-tenant" : "acme"
          },
          "x-tenant" : "acme"
        },
        "x-tenant" : "acme",
        "summary" : "Hello",
        "tags" : [ "Example Resource" ]
      }
    }
  },
  "info" : {
    "title" : "prout-quarkus API",
    "version" : "1.0-SNAPSHOT"
  }
}

Screenshots (if appropriate):

Before:

After:

Checklist

My PR contains...

• Bug fixes (non-breaking change which fixes an issue)

My changes...

• are not breaking changes.

Documentation

• My changes do not require a change to the project documentation.

Automated tests

• All new and existing tests passed.

[robert-hebel-sb]

could we rewrite and reuse logic from core/utils to filter extensions?

const extensionRegExp = /^x-/
export const isExtension = (key) => extensionRegExp.test(key)

export const getExtensions = (defObj) => {
  if(Map.isMap(defObj)) {
    return defObj.filter((v, k) => isExtension(k))
  }
  return Object.keys(defObj).filter((key) => isExtension(key))
}

Suggested change

	responses.filter((_, key) => !key.startsWith("x-")).entrySeq().map( ([code, response]) => {
	responses.filter((_, key) => !isExtension(key)).entrySeq().map( ([code, response]) => {

[robert-hebel-sb]

hey @DarkMatter-999
thanks for creating this PR 🙏

could we address an issue where we don't have any responses besides extension? Currently we display an empty table but no table should be displayed in such case

actual:

expected:

openapi: 3.1.0
paths:
  /hello:
    get:
      responses:
        x-tenant: acme

info:
  title: prout-quarkus API
  version: 1.0-SNAPSHOT

[DarkMatter-999]

Hi @robert-hebel-sb, thanks for the review.
I have made all the required changes, please re-review ✌️.

[swagger-bot]

🎉 This PR is included in version 5.29.4 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀