PRSUM-10218: Arrangement Manager Service API V3 Update

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.

[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.