feat(publishing-events): change Kafka event publishing keys for holdings and items.

[SvitlanaKovalova1]

Purpose

MODINVSTOR-1281 Currently, mod-search has an issue with processing events received from the mod-inventory-storage after creating a list of holdings for one Instance via the POST /holdings-storage/batch/synchronous endpoint.
The mod-inventory-storage publishes the list of events on creating holdings for an instance with the instanceId publishing key. So the list of events with the same instanceId publishing key are published.

The mod-search consumes events, groups them by key and processes only the one event, so in this case the rest events with the same instanceId key will not be processed and the data will not get into the holding table of the mod-search module.
The same issue with Items : POST /item-storage/batch/synchronous endpoint.
In order to avoid this issue, need to change the key for publishing events for holdings and items.

Approach

Kafka event publishing keys have been changed:

• for holdings with instanceId to holdingId;
• for items with instanceId to itemId.

Changes Checklist

• API Changes: Document any API paths, methods, request or response bodies changed, added, or removed.
• Database Schema Changes: Indicate any database schema changes and their impact. Confirm that migration scripts were created.
• Interface Version Changes: Indicate any changes to interface versions.
• Interface Dependencies: Document added or removed dependencies.
• Permissions: Document any changes to permissions.
• Logging: Confirm that logging is appropriately handled.
• Unit Testing: Confirm that changed classes were covered by unit tests.
• Integration Testing: Confirm that changed logic was covered by integration tests.
• Manual Testing: Confirm that changes were tested on local or dev environment.
• NEWS: Confirm that the NEWS file is updated with relevant information about the changes made in this pull request.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
91.5% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud