CP4BA 24.0.0 and IPM 1.15.0

[jandusek4]

• CP4BA upgraded to 24.0.0
• Process Mining upgraded to 1.15.0
• Usage configmap redesigned for better maintainability
• Added Studio routes and some other endpoints into usage
• Zen Api Key in header form generated in usage info in cpadminservice-zen-api-key entry which can be used in WxO directly
• BAI emitter enabled on BAWTOS object store to support BAI tracking when Client Onboarding demo is executed
• Debug pod added to deployment for better troubleshooting and also to give you Pod with tooling from start (for TZ Deployer options)
• PostgreSQL databases of CPFS IM, BTS and Zen added to CloudBeaver for troubleshooting or curiosity
• Added OpenSearch Dashboards connected to CP4BA OpenSearch instance

[gitguardian[bot]]

⚠️ 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.

🔎 Detected hardcoded secret in your pull request

| GitGuardian id | GitGuardian status | Secret | Commit | Filename | | | -------------- | ------------------ | ------------------------------ | ---------------- | --------------- | -------------------- | | [10070264](https://dashboard.gitguardian.com/workspace/135544/incidents/10070264?occurrence=149698778) | Triggered | Generic Password | dd762169765057caada8a77bd592c5e4e0d3f53f | automation-roles/50-install-cloud-pak/cp4ba/cp4ba-cluster/tasks/main.yml | [View secret](https://github.com/IBM/cloud-pak-deployer/commit/dd762169765057caada8a77bd592c5e4e0d3f53f#diff-8cda14d3bdbc8d90e7b9f6ca0b02380a500b7724e143eaba09e6cbc257ea3f39L123) |

🛠 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](https://blog.gitguardian.com/secrets-api-management?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) the best practices. 3. Revoke and [rotate this secret](https://docs.gitguardian.com/secrets-detection/secrets-detection-engine/detectors/generics/generic_password#revoke-the-secret?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 4. If possible, [rewrite git history](https://blog.gitguardian.com/rewriting-git-history-cheatsheet?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 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](https://blog.gitguardian.com/secrets-api-management/?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) for managing and storing secrets including API keys and other credentials - install [secret detection on pre-commit](https://docs.gitguardian.com/ggshield-docs/integrations/git-hooks/pre-commit?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) 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.}