pgsql: Put back explicit setting of replication values within TAP tests

Put back explicit setting of replication values within TAP tests.

Commit 151c0c5f7 neglected the possibility that a TEMP_CONFIG file
would explicitly set max_wal_senders=0; as indeed buildfarm member
thorntail does, so that it can test wal_level=minimal in other test
suites. Hence, rather than assuming that max_wal_senders=10 will
prevail if we say nothing, set it explicitly.

Set max_replication_slots=10 explicitly too, just to be safe.

Back-patch to v10, like the previous patch.

Discussion: /messages/by-id/723911.1601417626@sss.pgh.pa.us

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/49642530486852f8fef248964e563aaab25ecae7

Modified Files
--------------
src/test/perl/PostgresNode.pm | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)