Consider pg_ctl successful when progress is made

There is a race when using pg_ctl start --wait:

 - pg_ctl starts Postgres
 - Postgres begins recovery, detects a parameter requires restart, and exits
 - pg_ctl reports that Postgres did not start

Now we look at the LSN reported by pg_controldata to determine if Postgres
made any progress during a "failed" start.

Issue: PGO-1945

Author: cbandy

internal/pgbackrest/config.go

@@ -248,7 +248,10 @@ read -r max_wals <<< "${control##*max_wal_senders setting:}"
 echo >> /tmp/postgres.restore.conf "max_wal_senders = '${max_wals}'"
 fi
 
-pg_ctl start --silent --timeout=31536000 --wait --options='--config-file=/tmp/postgres.restore.conf'
+read -r stopped <<< "${control##*recovery ending location:}"
+pg_ctl start --silent --timeout=31536000 --wait --options='--config-file=/tmp/postgres.restore.conf' || failed=$?
+[[ "${started-}" == "${stopped}" && -n "${failed-}" ]] && exit "${failed}"
+started="${stopped}" && [[ -n "${failed-}" ]] && failed= && continue
 fi
 
 recovery=$(psql -Atc "SELECT CASE