feat: Allow File Storage database name to be customised

[ppawlowski]

Description

This pull request adds a possibility to specify custom database name used by the File Storage service.
Additionally, it removes hardcoded database username from the initialisation script.

Related Issue(s)

#305

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

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

[ppawlowski]

The failure in the lint workflow is acceptable due to the known error with the chart linting tool not using the new values file.

[hardillb]

@ppawlowski approved, my only question about this is if we are going this route should we also allow different host, port, username & password as well?

[ppawlowski]

@ppawlowski approved, my only question about this is if we are going this route should we also allow different host, port, username & password as well?

For file-storage configuration - we already allow for such approach.

For the initialisation script - it is scoped to run only against local postgres so only credentials can be changed - this is something we cover as well.

[hardillb]

Sorry, I meant running the ff-context db on a totally separate postgresql instance.

But don't worry about that now