test(winston, pino): fix tests to exclude agent logging that collides

In APM agent 3.13.0 it started using pino logging by default. That
affected one of the tests that intentionally starts the agent without
a "serviceName"... which leads to a log.error from the agent... which
broke the test that was looking for JSON-structured logging only from
the test script.

Author: trentm

loggers/pino/package.json

@@ -39,7 +39,7 @@
   "devDependencies": {
     "ajv": "^7.0.3",
     "ajv-formats": "^1.5.1",
-    "elastic-apm-node": "^3.10.0",
+    "elastic-apm-node": "^3.14.0",
     "express": "^4.17.1",
     "pino": "^6.0.0",
     "pino-http": "^5.3.0",

loggers/pino/test/use-apm-override-service-name.js

@@ -33,7 +33,8 @@ const apm = require('elastic-apm-node').start({
   serviceName,
   centralConfig: false,
   captureExceptions: false,
-  metricsInterval: 0
+  metricsInterval: 0,
+  logLevel: 'off'
 })
 
 const ecsFormat = require('../') // @elastic/ecs-pino-format

loggers/winston/package.json

@@ -41,7 +41,7 @@
     "ajv": "^7.0.3",
     "ajv-formats": "^1.5.1",
     "autocannon": "^7.0.1",
-    "elastic-apm-node": "^3.10.0",
+    "elastic-apm-node": "^3.14.0",
     "express": "^4.17.1",
     "split2": "^3.2.2",
     "standard": "16.x",

loggers/winston/test/use-apm-override-service-name.js

@@ -31,7 +31,8 @@ require('elastic-apm-node').start({
   serviceName,
   centralConfig: false,
   captureExceptions: false,
-  metricsInterval: 0
+  metricsInterval: 0,
+  logLevel: 'off'
 })
 
 const ecsFormat = require('../') // @elastic/ecs-winston-format