Add support for PostgreSQL 13
### Summary
PostgreSQL 13 is scheduled to be released in [the third quarter of 2020](https://www.postgresql.org/developer/roadmap/#:~:text=The%20next%20major%20release%20of,the%20third%20quarter%20of%202020.). We should add support for PG13 starting in %"14.0" when PG 11 is being removed, so that users wanting to benefit from the enhancements introduced in PG13 can easily do so.
See the [PG 12 epic](https://gitlab.com/groups/gitlab-org/-/epics/2374) for tasks that need to be completed. We will need to create a similar list of issues for this epic.
### Phased plan
* [x] In 13.12 add PG13 to CI testing to test for compatibility.
* [x] In 14.1 package PG13 in Omnibus and the Helm chart as an opt-in version for new, single node installs.
* [x] In %"14.5" and %"14.6" test PG13 with upgrades, multi node installs, failover with Patroni, and Geo and announce general support in %"14.10".
- [x] In `15.0` default to PostgreSQL 13 for new installs of GitLab
* [ ] In `15.11` auto upgrade users to PG13
* [ ] In `16.0` PG 13 becomes the minimum required version
### Requirements
* Test using PG13 in fresh installs and upgrades.
* Test the following install types:
* [x] Single node
* [x] Separate database node, omnibus managed
* [x] PG HA with 3 or more database nodes and Patroni
* [x] GEO with one primary node, one secondary node (postgresql and geo-postgresql on the same secondary node)
* [x] Geo and HA with one primary database node and one secondary database node (postgresql and geo-postgresql on the same secondary node).
* [x] Geo and HA with PG HA for the primary database node, one secondary database node (postgresql and geo-postgresql on the same secondary node)
* [x] Geo with one primary node, separate secondary nodes for postgresql, and geo-postgresql databases
* Test that backup and restore work
### Tasks
In summary, key tasks include:
* Include PostgreSQL 13 in the omnibus-gitlab package
* Verify application works on PostgreSQL 13
* At a minimum, we'll want to run gitlab-qa against an instance using PostgreSQL 13 on each of the install types.
* Verify backup and restore works.
* Verify upgrade from 12 -> 13
### Announcements
* Ensure we announce progress to GDK channels. GDK doesn't currently handle the upgrade so we should provide plenty of advanced notice about the upgrade timelines.
epic