Add support for PRODUCTION environment (not just development)

[w-le]

Currently all clusters will be deployed in development mode, which is insecure as it will use public secret stored in each service's git repo.

There should be a global value to specify whether to deploy the new cluster in development or production mode.

When in production mode, new JWT secret and public keys should be generated and stored as k8s secrets and shared to each relevant pod (which I think are api/staff, maybe core? someone from Product team will be able to confirm which services needs which env vars when in PRODUCTION mode)

In production mode there should be 0 "default" passwords, e.g. initial backoffice password should be randomly generated.

[viv-4]

• [ ] no default secrets
• [x] resource definitions - dev: https://github.com/place-labs/k8s-helm/commit/1a884ca8e3ac64691a498a143b933449eec42918 prod: https://github.com/place-labs/k8s-helm/commit/1a884ca8e3ac64691a498a143b933449eec42918
• [x] prod terraform (azure) - https://github.com/place-labs/k8s-terraform/commit/11266f2c1a6b304cdbf6bb1bf08a92b3dc9773b4
• [ ] scale placeos services
• [ ] scale external services
• [ ] should env (placeos services env var) be development on master?
• [ ] use global value rather than branches