Microsoft.OpenAPI 2.0 adds string type with pattern for int params. How to avoid?

[jornhd]

Microsoft.OpenAPI 2.0 adds string type with pattern for int params.
Example:

        "parameters": [
          {
            "name": "TypeId",
            "in": "query",
            "required": true,
            "schema": {
              "pattern": "^-?(?:0|[1-9]\\d*)$",
              "type": [
                "integer",
                "string"
              ],
              "format": "int32"
            }

This causes openapi-generator to create an object to handle both types, which is totally unnecessary in our case.
How can we avoid this behaviour?

[martincostello]

See #61038 (comment).