Replace configs appset with a helm template generator

[tomklapiscak]

This PR forms part of the work for https://jsw.ibm.com/browse/MASCORE-2082 to replace the use of the configs ApplicationSet with a Helm template-based generator. This was necessary for a couple of reasons:

• a bug in ArgoCD causes PostDelete hooks to not work for Applications generated directly by ApplicationSets
• the fact that ArgoCD does not honour syncwave annotations for applications generated by ApplicationSets (see slack thread for details)

In order to implement the Helm-template-based Application generator, I was forced to merge all of our MAS config files (MongoCfg, SLSCfg, etc etc) into a single list in a single file in gitops-envs. (ibm-mas-suite-configs.yaml, example)

This PR replaces all of the individual CLI functions for setting up MAS configs in their own files with a single function gitops-mas-config capable of maintaining the list in this single file. All configuration types (mongo, sls, etc) with any scope (system, app, ws, wsapp) can be upserted or removed idempotently by this single script. All of the associated Tekton tasks have also been updated to use this new function.

This PR also introduces the new clone_and_lock_target_git_repo and save_and_unlock_target_git_repo functions in gitops-utils that guard against merge conflicts that can happen when multiple instanves of the function for the same MAS instance are run in parallel. These functions are generic and will be suitable for use in other functions if we ever need to change them to update a single, shared config file in gitops-envs.

Associated PRs:

• Add MAS config CR PostDelete hooks. Replace configs appset with a helm template generator gitops#42
• https://github.ibm.com/maximoappsuite/saas-tekton/pull/10

Related Issues:

• https://jsw.ibm.com/browse/MASCORE-2082
• https://jsw.ibm.com/browse/MASCORE-1841
• https://jsw.ibm.com/browse/MASCORE-2124

Testing:

• Verified that the function works for all supported MAS config types/scopes by running it directly against a MAS cluster in Fyre
• Verified that the Tekton pipelines still work by running them against the fvtsaas cluster in AWS
  • gitops-mas-instance pipeline run
  • gitops-mas-apps pipeline run
  • Resulting ibm-mas-suite-configs.yaml and commit history:

• Resulting ArgoCD MAS instance-root app (unhealthy ma application unrelated to these changes, the relevant apps are highlighted):

• gitops-mas-apps-deprovision pipeline run
• gitops-mas-instance-deprovision pipeline run
• ibm-mas-suites-configs.yaml file deleted as expected once the final config was removed. Git commit history: