Establish production Postgres Connectivity to orbit-production
### Problem to Solve We need to establish PSC (consumers) on `orbit-production` so that connectivity is established for siphon to connect to postgres instances for `main`, `sec` and `ci` databases. We need to establish how/where the private service connection (PSC) definitions will be done for `database-gprd` because none exists so far in https://ops.gitlab.net/gitlab-com/gl-infra/config-mgmt/-/tree/main/environments/database-gprd?ref_type=heads. See previous work done in for staging: * https://gitlab.com/gitlab-org/analytics-section/siphon/-/work_items/174+ * https://gitlab.com/gitlab-org/orbit/knowledge-graph/-/work_items/203 For production @alexander-sosna has outlined an approach on https://gitlab.com/gitlab-com/gl-infra/data-access/dbo/dbo-issue-tracker/-/work_items/692+ and we need to make sure that all required pieces for this exist and if it can be moved forward. **NOTE:** The `ci` Patroni backend service was configured as `EXTERNAL` (global) with `balancingMode: UTILIZATION` in staging. PSC requires `INTERNAL` + `CONNECTION`. This is still the case in production and it was discussed that team needs to re-create it as regional first. This was observed earlier [here](https://gitlab.com/gitlab-org/orbit/knowledge-graph/-/work_items/203#note_3144593253) and it essentially is not-in use by any existing workload. ### Proposed Solution
issue