Investigate Data Foundation/Data Fabric/CP4D options

The current Data Foundation modules have been updated to use the gitops provider and gitea, however there is still work to bring cp4d modules where they need to be. Additional work includes:

- updating remaining cp4d software modules to use the gitops provider and gitea (data fabric modules, db2, etc...)
- update all cp4d modules for cp4d 4.5 (current modules are for cp4d 4.0)

We need to decide the approach for finishing up Data Foundation/Data Fabric modules.

## Options:
1. ❌ Update remaining cp4d modules for gitea & gitops provider, **targeting cp4d 4.0**.
- Shortest timeline to update remaining data fabric modules.
- Approximately 1 week's worth of effort to finish remaining modules
- Modules will still target a back-level version of CP4D, not the latest
- Does not re-use automation from the product team
2. ❌ Update all cp4d modules for gitea & gitops provider, **targeting cp4d 4.5**.
- Approximately 2-3 week's worth of effort to update all modules
- Modules will target latest version of CP4D
- Does not re-use automation from the product team, so we maintain our own deployment artifacts (not desirable)
- We can leverage cpd-cli to generate kube yaml (in preview.sh files), and we extract correct yaml by hand.
3. ✅ Update all cp4d modules to leverage Cloud Pak Deployer
- Rewrite all modules to leverage https://ibm.github.io/cloud-pak-deployer/
- May require an operator to manage Cloud Pak Deployer interactions (like MAS)
- Modules can target latest version of CP4D
- **Is not** supported by the product team
- Would be abstraction on top of abstraction (This leverages cpd-cli under the hood)
- At least 1+ month (optimistically)
4. ✅ Update all cp4d modules to leverage cpd-cli
- Rewrite all modules to leverage https://github.com/IBM/cpd-cli/
- May require an operator to manage cpd-cli interactions (like MAS)
- Modules can target latest version of CP4D
- **Is** supported by the product team
- At least 1+ month (optimistically)
- Duplication of effort (basically we'd be doing the same as the Cloud Pak Deployer, but in terraform instead of Ansible)