Teleport for GitLab CI Database

Details

• Point of contact for this request: @DylanGriffith
• If a call is needed, what is the proposed date and time of the call: Date and Time
• Additional call details (format, type of call): additional details

SRE Support Needed

After we finish CI decomposition (Currently planned for July 2nd) all writes (and the source of truth) for all CI tables will be in a separate database (currently patroni-ci cluster). This means that anybody that uses teleport to access the database console (https://gitlab.com/gitlab-com/runbooks/-/blob/master/docs/Teleport/Connect_to_Database_Console_via_Teleport.md) will not be able to see new data for CI tables and this may slow down debugging efforts. Likely we will just need to add DB hosts for db-secondary-ci and db-primary-ci that connect to:

1. ci-db-replica.service.consul
patroni-ci-03-db-gstg.c.gitlab-staging-1.internal (For gstg)
   patroni-ci-03-db-gprd.c.gitlab-production.internal (For gprd)
   
2. master.patroni-ci.service.consul