Do not consider semicolon as query param separator

[exalate-issue-sync]

The API uses a semicolon as a value separator for query parameters and then the ; is getting translated to &.

As it maybe a Breaking Change for some users, we will introduce a settings into the gravitee.yaml to define the behaviour to adopt.

To handle this without impacting other APIs that may need to handle semicolon as a separator, implement a new custom-query-parameters-parser policy: https://github.com/gravitee-io/gravitee-policy-custom-query-parameters-parser

How to test

• create an api
• add the policy in your flow
• do some calls with query parameters containing semicolon (for ewample ?filter=field1%20name;field2%20age)

Should also work in debug mode

Additional information

Policy is not part of the default bundle
you can find it here: https://download.gravitee.io/#graviteeio-apim/plugins/policies/gravitee-policy-custom-query-parameters-parser/