[OpenAPI] SecurityRequirement case class produces invalid open api json

[kdelija]

Describe the bug
When generating OpenApi json. SecurityRequirement adds securitySchemes object that is not a part of OpenApi 3.1.0 specification. For this reason, Swagger Ui is ignoring the security object and it is not forwarding the header/apiKey that is defined to the backend.

To Reproduce
Steps to reproduce the behaviour:
Go to OpenAPISpec test. In the expected result you see security defined as

  "security" : [
    {
      "securitySchemes" : {
        "apiKeyAuth" : []
      }
    }
  ]

Expected behaviour
The test is passing because this is not a valid OpenApi 3.1.0 json. If you read the speficifation you will see that securitySchemes is redundant and the test should look like this:

  "security" : [
    {
      "apiKeyAuth" : []
    }
  ]