DRAFT: Updated MXD to use EDC 0.8.0rc2

[ieuna]

Please do not merge this PR.
This setup of MXD is using SAP DIM. The open-source wallet is not compatible with latest versions of EDC. So, creating and testing a full setup of MXD is not possible at the moment.

Description

1. Updated MXD to use EDC 0.7.1/0.8.0rc2.
2. Updated Backend Service to use EDC 0.7.1/0.8.0rc2.
3. Added new endpoint to backend service for processing transfer events(for 0.7.1 and above)
4. Updated Terraform/K8 configs.
5. Updated Postmam schema.
6. Updated Jmeter Script to use backend service and new schema.
7. Updated documentation to include purpose of backend service, and on how to use backend service image for performance test.

Missing Components

• Either MIW or an open-source wallet.
• Integration test for new backend service endpoint(mentioned above).

Pre-review checks

Please ensure to do as many of the following checks as possible, before asking for committer review:

• DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
• Copyright and license header are present on all affected files

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
13321946	Triggered	Generic Private Key	6b09127	mxd/performance-tests/prometheus/prometheus-ingress.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}