Chk 3279 change stream

[CianoDanilo]

List of Changes

Motivation and Context

This is the first implementation of a change data capture mechanism for the payment wallet domain.
This application will listen to the wallet log events collection for change events and then sends them to a queue.

How Has This Been Tested?

It has been tested with jUnit tests and monitored after release in DEV env

Screenshots (if appropriate):

Types of changes

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

[infantesimone]

to reduce the number of changed lines in a PR, in general, if you encounter errors/bug that are not related to PR, it is better to resolve them in dedicated PR (I see changes to the pipeline configuration and helm values ​​in uat)

[sonarqubecloud]

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

[infantesimone]

great! 🚀🚀🚀

[github-actions]

Pull request label validation error!
Required label for app version: patch,minor,major,ignore-for-release
Required label for chart version: chart-patch,chart-minor,chart-major.

Found labels on PR...

app version:
chart version:

If you want to skip release for this PR add skip-release label