Increase timeout for Postgres starting with Patroni (or make it configurable)
Currently in Omnibus when using Patroni and Postgres we have a hardcoded timeout of 30s for Postgres start.
This time isn't sufficient for all scenarios. In our testing we've regularly seen it triggered when the Postgres node in question needs to replicate data as it starts up, preventing it from being ready in time.
We need to increase this timeout to probably something quite high or figure out a way to make it intelligently tell that Postgres is replicating and to wait for it to finish.