Update Swagger definition in order to be compatible with string identifiers

[phansys]

Subject

Update OpenAPI (Swagger) definition in order to be compatible with string identifiers (like UUIDs).

These changes are consistent with the API narrowing made at sonata-project/admin-bundle (see AdminInterface::id()).

I am targeting this branch, because these changes respect BC.

Changelog

### Removed
- Removed requirements that were only allowing integers for model identifiers at Open API definitions.
### Fixed
- Fixed support for string model identifiers at Open API definitions.

[phansys]

@wbloszyk, could you please confirm if the sandbox is working fine without these restrictions?

[wbloszyk]

@wbloszyk, could you please confirm if the sandbox is working fine without these restrictions?

In @ApiDoc this restriction in only like information for people. It will be work but you should keep "dataType"="integer|UUIDs". Restriction will be when you add it in @Route and @ApiDoc will read this and display descriptions for people from it.

[phansys]

In @apidoc this restriction in only like information for people.

AFAIK, the @apidoc annotations are used to build the Open API Specification, which is consumed by the built-in sandbox to display the information which you are referencing and to create the "Try it out" forms. It also can be consumed by 3rd party compatible clients.

[phansys]

If you can, please check the resulting definition at Swagger Editor. You can also play with the changes you're proposing in order to check if the result works as expected.

It will be work but you should keep "dataType"="integer|UUIDs"

I wouldn't use "UUID" as type, since their type is really a string.

[wbloszyk]

For swagger for path parameter you have to:

@SWG\Parameter(name="id", in="path", type="string")

Type must be "string", "number", "integer", "boolean", "array", "file".
"string" works becouse it is convert to url but probably it is not good idea.
"integer" will not allow use string.

[phansys]

"string" works becouse it is convert to url but probably it is not good idea.

Why do you think is not a good idea? IMO, we could use type="string" in conjunction with pattern attribute in order to keep narrowed the allowed values.

[SonataCI]

Could you please rebase your PR and fix merge conflicts?

[wbloszyk]

Thanks @phansys