Fix deployment script for environment OC_NAMESAPCE

[ianliuwk1019]

Describe the Bug
FOM production has a failure on Sept 13 for two batch jobs (workflow change/forest client refresh) and that caused business to report some FOM (ID: 1827) the status did not get changed to commenting open in the morning (batch job run) and still remained in PUBLISHED.

After team troubleshooting together, the discovery was both production and test environments all are pulling image from "-dev" space (from OC_NAMESPACE config).

The root cause was the recent PR change for the openshift deployment yml script to referencing the OC_NAMESPACE from Github environment/secret instead of previous hardcoded namespace value. This change did not work for TEST and PROD.
From the Github action environment/secret that there was still a default repository (${OC_NAMESPACE}) value and during deployment it seems the deployment(test/prod) all gets the (OC_NAMESPACE) value from the default repository value, although there were OC_NAMESPACE configured value setup in Github for other environments (-test/-prod).

Expected Behaviour
${OC_NAMESPACE} should referencing the correct value from environment specific.

Actual Behaviour
It was always the "dev" (the default one at the repository secret).

Action to take

• Either revert back to previous configuration for using direct hardcode name space for each environment deployment at configuration, or get rid of Github repository (default) OC_NAMESPACE variable and add environment for -dev environment at openshift yaml to referencing the correct value from Github for all environments (dev/test/prod).

Additional context
Add any other context about the problem here.