SSH retry limit (do not reset the attempt counter)

SSH retry limit (do not reset the attempt counter)

Fixed: https://gitlab.com/postgres-ai/postgresql-consulting/tests-and-benchmarks/-/jobs/6520863003

What's new

• Avoid the situation of an endless "connection attempt", make the number of retries fixed (max_attempts)
• Increase the 'ConnectTimeout' to 60 (1min) to attempt to create an SSH connection
  • it makes sense for stress testing when the target server is under high load
• Add a timestamp to the "connection attempt" message

Example: https://gitlab.com/postgres-ai/postgresql-consulting/tests-and-benchmarks/-/jobs/6522512923

92110400 of 100000000 tuples (92%) done (elapsed 255.35 s, remaining 21.87 s)
94526600 of 100000000 tuples (94%) done (elapsed 260.02 s, remaining 15.06 s)
97210500 of 100000000 tuples (97%) done (elapsed 265.53 s, remaining 7.62 s)
99508900 of 100000000 tuples (99%) done (elapsed 270.01 s, remaining 1.33 s)
100000000 of 100000000 tuples (100%) done (elapsed 270.46 s, remaining 0.00 s)
vacuuming...
creating primary keys...
2024-04-01 19:07:01 WARNING: Connection terminated, reconnection attempt... (1 from 30).
creating primary keys...
2024-04-01 19:07:25 WARNING: Connection terminated, reconnection attempt... (2 from 30).
creating primary keys...
2024-04-01 19:07:39 WARNING: Connection terminated, reconnection attempt... (3 from 30).
creating primary keys...
done in 350.47 s (drop tables 0.00 s, create tables 0.01 s, client-side generate 271.79 s, vacuum 0.20 s, primary keys 78.47 s).