feat: Openshift container changes

[hardillb]

Description

Ensures the Node-RED stack containers will allow for npm install on OpenShift

Also adds some resource constraints to the db upgrade job container. (Still need to test the upgrade on OpenShift)

Related Issue(s)

Checklist

• I have read the contribution guidelines
• Suitable unit/system level tests have been added and they pass
• Documentation has been updated
  • Upgrade instructions
  • Configuration details
  • Concepts
• Changes flowforge.yml?
  • Issue/PR raised on FlowFuse/helm to update ConfigMap Template
  • Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production

Labels

• Backport needed? -> add the backport label
• Includes a DB migration? -> add the area:migration label

[hardillb]

OK, I know why Node-RED 2.2.x container failed. I'm going to say that 2.2 is not supported on OpenShift (we will drop it when 4.0 ships anyway)

[hardillb]

@ppawlowski Can you look why the test failed? I can see in the logs that the file-server failed because the ff-context db can't be found. But I can't find the logs for the upgrade job running in the output to see why it failed to create the db

[hardillb]

@ppawlowski Thanks, I should have tried updating the base branch

[ppawlowski]

For unknown reasons, there are no job logs in the chart testing output. At least I was not able to find it.
In general, this output is quite noisy and sometimes hard to find the root cause...