fix: Use file-server container for db upgrade job

[hardillb]

fixes #306

Description

While testing installing on OpenShift the db upgrade job fails because it's no longer run as the root user so can't install the psql command into the alpine container image.

This adds the psql command to the file-server image and uses this to run the job.

Related Issue(s)

#306

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

[github-actions]

node-red:2.2.3-main-linux-amd64 scan results

26 tests    0 ✅  0s ⏱️
 4 suites   0 💤
 1 files    26 ❌

For more details on these failures, see this check.

Results for commit 71218ab.

♻️ This comment has been updated with latest results.

[github-actions]

node-red:3.0.2-main-linux-amd64 scan results

 1 files  4 suites   0s ⏱️
 9 tests 0 ✅ 0 💤  9 ❌
10 runs  0 ✅ 0 💤 10 ❌

For more details on these failures, see this check.

Results for commit 71218ab.

♻️ This comment has been updated with latest results.

[github-actions]

node-red:3.1.x-main-linux-amd64 scan results

8 tests   0 ✅  0s ⏱️
4 suites  0 💤
1 files    8 ❌

For more details on these failures, see this check.

Results for commit 71218ab.

♻️ This comment has been updated with latest results.

[github-actions]

file-server:main-linux-amd64 scan results

1 tests   0 ✅  0s ⏱️
6 suites  0 💤
1 files    1 ❌

For more details on these failures, see this check.

Results for commit 71218ab.

♻️ This comment has been updated with latest results.

[github-actions]

node-red:3.0.2-main-linux-arm64 scan results

 1 files  4 suites   0s ⏱️
 9 tests 0 ✅ 0 💤  9 ❌
10 runs  0 ✅ 0 💤 10 ❌

For more details on these failures, see this check.

Results for commit 71218ab.

♻️ This comment has been updated with latest results.

[github-actions]

node-red:2.2.3-main-linux-arm64 scan results

26 tests    0 ✅  0s ⏱️
 4 suites   0 💤
 1 files    26 ❌

For more details on these failures, see this check.

Results for commit 71218ab.

♻️ This comment has been updated with latest results.

[github-actions]

node-red:3.1.x-main-linux-arm64 scan results

8 tests   0 ✅  0s ⏱️
4 suites  0 💤
1 files    8 ❌

For more details on these failures, see this check.

Results for commit 71218ab.

♻️ This comment has been updated with latest results.

[github-actions]

file-server:main-linux-arm64 scan results

1 tests   0 ✅  0s ⏱️
6 suites  0 💤
1 files    1 ❌

For more details on these failures, see this check.

Results for commit 71218ab.

♻️ This comment has been updated with latest results.

[github-actions]

forge-k8s:main-linux-amd64 scan results

1 tests  ±0   0 ✅ ±0   0s ⏱️ ±0s
4 suites ±0   0 💤 ±0 
1 files   ±0   1 ❌ ±0 

For more details on these failures, see this check.

Results for commit 71218ab. ± Comparison against base commit b3cd583.

♻️ This comment has been updated with latest results.

[github-actions]

forge-k8s:main-linux-arm64 scan results

1 tests  ±0   0 ✅ ±0   0s ⏱️ ±0s
4 suites ±0   0 💤 ±0 
1 files   ±0   1 ❌ ±0 

For more details on these failures, see this check.

Results for commit 71218ab. ± Comparison against base commit b3cd583.

♻️ This comment has been updated with latest results.

[hardillb]

I assume the validation failed because the file-server container wasn't built?

https://github.com/FlowFuse/helm/actions/runs/7870917055/job/21473105621?pr=307#step:10:561

[hardillb]

@ppawlowski Just checking, the failed job looks to be using the latest containers from the docker hub, not the ones built as part of the PR test, so the failure is because the new version of the container is not published yet?

[hardillb]

I'll test this when I get chance locally