Update OpenShift Secrets During "Release - Deploy All"

[andrewsignori-aot]

We must ensure the OpenShift is always updated prior to deployment, which means every time the GHA Release - Deploy All is executed, it can invoke (prior to its execution) the Env Setup - Deploy SIMS Secrets to Openshift. This would reduce the actions needed during regular deployments (TEST/Staging/PROD) and also a "race" condition when the build and deploy happens to the DEV environment and the secrets must be deployed while the build is happening and before the POD deploy starts.

Acceptance criteria

• Use an action call in the same way that is done for the forms and Camunda definitions deploy to invoke the deployment of the secret.
• Run the secrets deployment in parallel with run-db-migrations.
• Keep the deployment of the current secret as it is to allow the release rollback to be executed.