sync-install configmap should be reset when install pipeline starts

[durera]

MAS CLI version

11.12.0

CLI function used

install

What happened?

If we re-run a failed install the sync-install configmap is not reset, this leads to problems when syncronizing parallel pipelines (such as FVT) because they will immediately see that the install has failed from the update made in the previous run.

We need to delete this configmap (if it exists) before the pipeline starts. I don't think we need to do it in the pipeline itself, the CLI should do this in launchInstallPipeline

Relevant log output

Inputs
------------------------------------------------------------------
Namespace .................. mas-fvtuninstall-pipelines
Config Map ................. sync-install
Config Map Key ............. INSTALL_STATUS
Config Map Initial Value.... 
Config Map Target Value..... Completed,Succeeded
Escape Config Map .......... sync-install
Escape Config Map Key ...... INSTALL_STATUS
Max Retries ................ 50
Delay ...................... 600
Ignore Failure ............. False


Status of sync-install
------------------------------------------------------------------
apiVersion: v1
data:
  INSTALL_STATUS: Failed
kind: ConfigMap
metadata:
  creationTimestamp: "2024-12-10T15:39:41Z"
  name: sync-install
  namespace: mas-fvtuninstall-pipelines
  resourceVersion: "55066"
  uid: e76adbc4-4fd5-4486-be67-5bf98a6fe3c0


Waiting for configmap/sync-install in mas-fvtuninstall-pipelines to contain key 'INSTALL_STATUS' ...

Waiting for configmap/sync-install in mas-fvtuninstall-pipelines to contain key 'INSTALL_STATUS' with value 'Completed,Succeeded' ...
[1/50] INSTALL_STATUS=Failed does not equal 'Completed,Succeeded' yet in configmap/sync-install.  Waiting 600 seconds before checking again
[1/50] configmap/sync-install indicates that the pipeline we are synchronizing with has already completed: Failed

Failed to locate key INSTALL_STATUS in configmap/sync-install with value 'Completed,Succeeded'