test: scale keepalive timeouts for slow machines

The test was using fixed timeouts and that seems to be causing sporadic
test failures on pi1-docker host (which is a very slow machine.)
Fixes: #30828
PR-URL: #30834
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Gabriel Schulhof <gabriel.schulhof@intel.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>

Author: bnoordhuis

test/sequential/test-https-server-keep-alive-timeout.js

@@ -34,13 +34,13 @@ test(function serverKeepAliveTimeoutWithPipeline(cb) {
 common.mustCall((req,res)=>{
 res.end();
 },3));
-server.setTimeout(500,common.mustCall((socket)=>{
+server.setTimeout(common.platformTimeout(500),common.mustCall((socket)=>{
 // End this test and call `run()` for the next test (if any).
 socket.destroy();
 server.close();
 cb();
 }));
-server.keepAliveTimeout=50;
+server.keepAliveTimeout=common.platformTimeout(50);
 server.listen(0,common.mustCall(()=>{
 constoptions={
 port: server.address().port,
@@ -57,13 +57,13 @@ test(function serverKeepAliveTimeoutWithPipeline(cb) {
 
 test(functionserverNoEndKeepAliveTimeoutWithPipeline(cb){
 constserver=https.createServer(serverOptions,common.mustCall(3));
-server.setTimeout(500,common.mustCall((socket)=>{
+server.setTimeout(common.platformTimeout(500),common.mustCall((socket)=>{
 // End this test and call `run()` for the next test (if any).
 socket.destroy();
 server.close();
 cb();
 }));
-server.keepAliveTimeout=50;
+server.keepAliveTimeout=common.platformTimeout(50);
 server.listen(0,common.mustCall(()=>{
 constoptions={
 port: server.address().port,