Consider allowing int for number type

[jseparovic1]

Jane version(s) affected: 7.5 using open-api-2

Description
Given following path in OpenAPI 2.0 schema:

{
    "/v1/accounts": {
      "get": {
        "summary": "List accounts",
        "operationId": "getV1Accounts",
        "description": "Lists registered accounts",
        "parameters": [
          {
            "type": "number",
            "description": "Page number (zero indexed, so use 0 for first page)",
            "default": 0,
            "minimum": 0,
            "maximum": 1048576,
            "name": "page",
            "in": "query"
          },
          {
            "type": "number",
            "description": "How many entries per page",
            "default": 20,
            "minimum": 1,
            "maximum": 1000,
            "name": "pageSize",
            "in": "query"
          },
        ]
    }
}

Result

1. It creates following query options resolver:

protected function getQueryOptionsResolver(): \Symfony\Component\OptionsResolver\OptionsResolver
    {
        $optionsResolver = parent::getQueryOptionsResolver();
        $optionsResolver->setDefined(['page', 'pageSize']);
        $optionsResolver->setRequired([]);
        $optionsResolver->setDefaults(['page' => 0, 'pageSize' => 20]);
        $optionsResolver->addAllowedTypes('page', ['float']);
        $optionsResolver->addAllowedTypes('pageSize', ['float']);
        return $optionResolver;
}

Using the client results in bad DX:

$client->getV1Accounts(); // Exception `int` provided but `float` is expected.
$client->getV1Accounts(queryParameters: ['page'=> 0.0, ''pageSize' => 20.0]); // Works fine.

Possible Solution
Allow to use int in case of number and then cast it.

Additional context
According to OpenAPI specification [1] OpenAPI has two numeric types, number and integer, where number includes both integer and floating-point numbers.

• [1] https://swagger.io/docs/specification/data-models/data-types/#numbers