lib,test: parameterize worker resource tests

Based on the new way of propagating worker initialization
failures, modify the tests so as to get specialized
error messages.

lib/internal/errors.js

@@ -1363,7 +1363,7 @@ E('ERR_WORKER_INVALID_EXEC_ARGV', (errors, msg = 'invalid execArgv flags') =>
   `Initiated Worker with ${msg}: ${errors.join(', ')}`,
   Error);
 E('ERR_WORKER_NOT_RUNNING', 'Worker instance not running', Error);
-E('ERR_WORKER_OUT_OF_MEMORY', 'Worker terminated due to reaching memory limit',
+E('ERR_WORKER_OUT_OF_MEMORY', 'Worker terminated due to reaching memory limit: %s',
   Error);
 E('ERR_WORKER_PATH',
   'The worker script filename must be an absolute path or a relative ' +

test/parallel/test-worker-resource-limits.js

@@ -25,7 +25,7 @@ if (!process.env.HAS_STARTED_WORKER) {
   }));
   w.on('error', common.expectsError({
     code: 'ERR_WORKER_OUT_OF_MEMORY',
-    message: 'Worker terminated due to reaching memory limit'
+    message: 'Worker terminated due to reaching memory limit: JS heap Out of Memory'
   }));
   return;
 }