[minor] Facilties(MREF) backup and restore

[sanjayprab]

Description

• suite_app_backup and suite_app_restore changes to onboard Facilities(MREF) to backup and restore.
  • Namepace and pvcs are backed up and restored.
  • for restore, facilitiesworkspace instance is first deployed and wait for it to become ready, allowing the operators to create deployments & statefulsets and its pvcs, then using podtemplates, the deployments and statefulsets are scaled down. Dummy pods are created to mount each pvc and default pvc data is deleted and restored from backup(file permissions and owner are restored as well). Then the dummy pods are deleted and podtemplates is removed.
• Enhancements to db2 backup and restore, mainly pausing the db2 probes during backup and restore operation to prevent db2 container from restarting due to liveness/readiness probes failing. this is a known symptom when db2 connections are removed to take offline backup the probes begin to fail and when backup/restore takes longer for larger dbs, the probes failures hit the threshold and the container is restarted.
• download_backup_archive and upload_backup_archive roles now support facilities archive files
• suite_app_backup and suite_app_restore READMEs are updated

python-devops - ibm-mas/python-devops#336

Test Results

---

⚠️ Notes for Reviewers

• Ensure you have understood the PR guidelines in the Playbook before proceeding with a review.
• Ensure all sections in the PR template are appropriately completed.