[major] Add junitreporter sub-chart for reporting sync to devopsdb

[whitfiea]

Adds a new sub-chart which is included in each argo app/helm chart we have. This new sub-chart called junitreporter has a presync and postsync job. The presync job will call the register-start.py script and create a configmap (if it doesn't exist) with the current time in. The register-start.py also has changes in the (ibm-mas/cli#1271) cli PR to accept the new ibm-mas-gitops productid. This will store that a sync job is started in the devops db.

The postsync of this new subchart runs when the main app chat completes its sync. This will call the save-junit-to-mongo script after creating a junit xml based test result (with just one testcase of sync). The configmap with the sync_start is used to determine the time taken. The configmap is then deleted by the post-sync job.

The reason the configmap is created by the job rather than as a resource is that when an app fails on sync it will re-sync and so the pre-sync is called again before the post-sync is called. This would reset the time in the configmap if it was a pure resource in the template.

Exmaple of a sync with the pre and post jobs:

The sub-chart will only be executed when the devops_mongo_uri is present.

WARNING: Although the sub-chart won't be used in envs that don't have devops_mongo_uri set, it will still need to template the subchart. This requires that the Vault Plugin being used in ArgoCD needs to run helm dependency update otherwise the helm template will error. The updated Vault Plugin config is present in the cli PR (ibm-mas/cli#1271). This is why this PR is marked as major as this needs to be in place regardless as to if the function will be used or not.