Implement zero-downtime major upgrades (blue/green)

[vitabaks]

In the previous release (1.8.0), we introduced automation for in place major upgrades with minimal downtime (see PR #301).
While this was a significant improvement, there is still a need for a solution that enables zero-downtime upgrades.

Proposed Enhancement: To achieve zero downtime during major PostgreSQL upgrades, we need to implement a feature that utilizes pg_upgrade on a standby cluster.

This approach involves the following steps (in short, without details):

1. Setting up a standby cluster (with pg_basebackup or from backup);
2. Synchronize the standby cluster with the source cluster using physical replication;
3. Create logical replication slot on the source database (and save LSN);
4. Promote the target cluster to LSN from logical replication slot;
5. Perform pg_upgrade on the target cluster;
6. Synchronize the target cluster with the source cluster using logical replication (apply changes);
7. Perform a switchover to target cluster with near-zero downtime;
8. Configure reverse logical replication for the possibility of rollback without data loss.

This method will allow us to perform major version upgrades without impacting the availability of the PostgreSQL service. With the ability to quickly rollback without losing the latest changes.

---

Consider sponsoring the project via GitHub or Patreon

[vitabaks]

If you're interested in this feature, please consider becoming a sponsor.

The development of this feature requires sponsorship to fund developer efforts. If you're already a sponsor and are interested in this feature, please leave a comment here so we can prioritize this issue accordingly.

We also welcome contributions from those willing to dedicate their time to implement this feature on a voluntary basis. Please see the Contributing Guide for more information.