Increase postgresql start and stop timeouts

The default timeout of pg_ctl is 60s which applies to both start and stop. I did hit this timeout while stopping and starting an already synced haf node on HDD which corrupted the hived due to bad shutdown.

While starting the node this is the error I was getting:

+ /etc/init.d/postgresql start
 * Starting PostgreSQL 14 database server
 * Error: /usr/lib/postgresql/14/bin/pg_ctl /usr/lib/postgresql/14/bin/pg_ctl start -D /home/hived/datadir/haf_db_store/pgdata -l /var/log/postgresql/postgresql-14-main.log -s -o -c unix_socket_directories="/var/run/postgresql" -c config_file="/etc/postgresql/14/main/postgresql.conf"  exited with status 1: 

2023-09-11 20:34:20.680 UTC [58] LOG:  starting PostgreSQL 14.7 (Ubuntu 14.7-0ubuntu0.22.04.1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, 64-bit
2023-09-11 20:34:20.680 UTC [58] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2023-09-11 20:34:20.680 UTC [58] LOG:  listening on IPv6 address "::", port 5432
2023-09-11 20:34:20.717 UTC [58] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-09-11 20:34:20.753 UTC [59] LOG:  database system was shut down in recovery at 2023-09-11 20:11:27 UTC
2023-09-11 20:34:20.755 UTC [59] LOG:  database system was not properly shut down; automatic recovery in progress
2023-09-11 20:34:20.768 UTC [59] LOG:  redo starts at 237/994ED68
pg_ctl: server did not start in time
   ...fail!

I tried adding the PGCTLTIMEOUT=10000 env variable to both docker_entrypoint and setup_postgres scripts which didn't increase the timeout. I had to replace the start command i.e. /etc/init.d/postgresql start in the setup_postgres file with the following:

sudo --user=postgres -n /usr/lib/postgresql/14/bin/pg_ctl start -D /home/hived/datadir/haf_db_store/pgdata -l /var/log/postgresql/postgresql-14-main.log -s -o "-c unix_socket_directories=/var/run/postgresql -c config_file=/etc/postgresql/14/main/postgresql.conf" -t 10000

-t is the argument for timeout. With this change I was able to get past the error and it took around 5-10 minutes to start the postgresql and I got to hived after that.

I didn't find another way to increase the pg_ctl timeout. We also need to increase the default timeout in run_hived_img from 180s to something like 10-15minutes. Maybe even more. I couldn't measure the time it takes to shutdown the node because my hived broke so I have to replay again.

cc @bwrona