[IOPAE-808]bugfix: remove version from cms api response and documentation

[StefanoDoc]

the version field does not exist in services cms , the service cms api do not return version on response

List of Changes

• remove version field from services cms api and documentation

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Chore (nothing changes by a user perspective)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[github-actions]

Jira Pull Request Link

This Pull Request refers to the following Jira issue IOPAE-808

[gunzip]

These are breaking changes that needs a major version upgrade of OpenAPI specs.

Who's the consumer of this APIs?

[StefanoDoc]

for the version field this is a optional field on a response , and is an OpenAPI bug that we forgot and left there, the cms api don't return version in response , for the max_allowed_payment_amount i agree , and for now i reverted it , @iwoak do you think we need to deprecate this field first ?

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information