Added zalando database support for rest of the geoweb backends

[Jusaa]

Add support for using Zalando databases for geoweb presets, taf and warnings backends. This is basically copy from earlier PR where support was added to opmet-backend, so copying the descriptions from there: #39

Added option to use Zalando Operator Postgres database instead of connection string to external database

• If useZalandoOperatorDb == true
  • Add postgresql resource
  • Use generated username & password created by postgresql resource to automatically set PRESETS_BACKEND_DB, AVIATION_TAF_BACKEND_DB and WARNINGS_BACKEND_DB instead of using db_secret
  • Don't generate db secret using db_secret
• If useZalandoOperatorDb == false
  • No changes except for changed default database name (and encoded database string)
• cleanInstall determines if database is started clean or restored from a backup

How to test:

• Code review
• Applications are deployed and used in https://terraform.opengeoweb.com instance, and the deployed backends are running at https://terraform.opengeoweb.com/taf, https://terraform.opengeoweb.com/presets and https://terraform.opengeoweb.com/warnings and the deployments can be inspected in test-geoweb cluster @intlgeoweb AWS account!

Closes https://gitlab.com/opengeoweb/fmi/fmi-aws-config/-/issues/118 & https://gitlab.com/opengeoweb/fmi/fmi-aws-config/-/issues/196 & https://gitlab.com/opengeoweb/fmi/fmi-aws-config/-/issues/197

[EarthModule]

GJ! Approved!