Update OpenShift Secrets During "Release - Deploy All"

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](https://github.com/bcgov/SIMS/blob/7e018bafc6325d8a6569ecae4c0e002177f61f04/.github/workflows/release-deploy-all.yml#L250-L269) to invoke the deployment of the secret.
- [ ] Run the secrets deployment in parallel with [run-db-migrations](https://github.com/bcgov/SIMS/blob/7e018bafc6325d8a6569ecae4c0e002177f61f04/.github/workflows/release-deploy-all.yml#L105).
- [ ] Keep the deployment of the current secret as it is to allow the release rollback to be executed.

Start in .github/workflows/release-deploy-all.yml, reviewing the run-db-migrations entry and the forms and Camunda definitions deploy action call around the linked lines. Confirm how Env Setup - Deploy SIMS Secrets to Openshift is invoked, then verify that the secrets deployment runs in parallel with run-db-migrations while the current secret deployment remains available for rollback. Done means all three acceptance criteria are satisfied.

Written by the indexing model from the issue text.