Remove pgbench "progress" test pending solution of its timing issues.

Buildfarm member skink shows that this is even more flaky than
I thought.  There are probably some actual pgbench bugs here
as well as a timing dependency.  But we can't have stuff this
unstable in the buildfarm, it obscures other issues.

src/bin/pgbench/t/001_pgbench_with_server.pl

@@ -445,28 +445,6 @@ sub check_pgbench_logs
 	ok(unlink(@logs), "remove log files");
 }
 
-# note: --progress-timestamp is not tested
-pgbench(
-	'-T 2 -P 1 -l --log-prefix=001_pgbench_log_1 --aggregate-interval=1'
-	  . ' -S -b se@2 --rate=20 --latency-limit=1000 -j ' . $nthreads
-	  . ' -c 3 -r',
-	0,
-	[   qr{type: multiple},
-		qr{clients: 3},
-		qr{threads: $nthreads},
-		qr{duration: 2 s},
-		qr{script 1: .* select only},
-		qr{script 2: .* select only},
-		qr{statement latencies in milliseconds},
-		qr{FROM pgbench_accounts} ],
-	[ qr{vacuum}, qr{progress: 1\b} ],
-	'pgbench progress');
-
-# $nthreads threads, 2 seconds, but due to timing imprecision we might get
-# only 1 or as many as 3 progress reports per thread.
-check_pgbench_logs('001_pgbench_log_1', $nthreads, 1, 3,
-	qr{^\d+ \d{1,2} \d+ \d+ \d+ \d+ \d+ \d+ \d+ \d+ \d+$});
-
 # with sampling rate
 pgbench(
 '-n -S -t 50 -c 2 --log --log-prefix=001_pgbench_log_2 --sampling-rate=0.5',