PRSUM-10218: arrangement-manager service V3 implementation

[daniel-chiuratto-seabra]

Description

Arrangement Manager API has been updated to V3, impacting its dependencies as follows:

• User Preferences Update Operations: These operations are no longer available. Since they were internal, the related POST and PUT endpoints have been removed. Consequently, any processes that involved creating or updating User Preferences have also been eliminated.
• Arrangement Batch Upsert Operation: This operation has been removed from the service-api layer and is now only available in the integration-api layer. It is primarily used for data ingestion by banks into Backbase’s platform. All data ingestion streams now use the integration-api for this purpose. The only change required is to use a different endpoint.
• Retrieving Arrangements: In V3, calls to retrieve a list of arrangements or an arrangement by ID can now be made using the new POST /service-api/v3/arrangements/searches endpoint. This endpoint provides multiple ways to retrieve arrangements through a single API call.
• Product Kind Operations: Only GET operations are now available for Product Kinds. The database management has been deprecated, as Product Kind data is now maintained statically through a YAML settings file in Arrangement Manager. As a result, POST and PUT endpoints are no longer available.

Checklist

• [X] I made sure, I read CONTRIBUTING.md to put right branch prefix as per my need.
• [X] I made sure to update CHANGELOG.md.
• [ ] I made sure to update Stream Wiki(only valid in case of new stream module or architecture changes). ~ N/A
• [X] My changes are adequately tested.
• [X] I made sure all the SonarCloud Quality Gate are passed.

[daniel-chiuratto-seabra]

Still requires to work in the composition project that are failing the tests below:

• ProductControllerIT.pullIngestArrangement_Success
• ProductControllerIT.pullIngestArrangement_Fail

There is a composition spec that still calling the old service-api v2 from arrangement-manager but I don't know yet how to proper update that.

[sonarcloud[bot]]

Quality Gate failed

Failed conditions
49.3% Coverage on New Code (required ≥ 80%)

See analysis details on SonarCloud

[daniel-chiuratto-seabra]

This Pull Request is being closed because this branch is outdated and I was requested to implement the update from master instead. Did the update there and opened another PR, so closing this one.