Add option to downgrade Timeout/Deadline error

[sgohlke]

If OpenTelemetry is used with an exporter like "@opentelemetry/exporter-trace-otlp-grpc" and there are network issues it might happen that the diagnose logger logs this as error message. According to open-telemetry/opentelemetry-js#3740 (comment) this can be ignored or downgraded.

TODO:

• Provide option to set force loglevel for messages "Service request"
• Provide option to set force loglevel for messages "4 DEADLINE_EXCEEDED" and "14 UNAVAILABLE"

Example message to be filtered/loglevel reduced:

"{\"stack\":\"Error: 14 UNAVAILABLE: No connection established\\n    at t.callErrorFromStatus 
(/app/instrumentation.js:2:38636)\\n    at Object.onReceiveStatus (/app/instrumentation.js:2:63920)\\n    at 
Object.onReceiveStatus (/app/instrumentation.js:2:59809)\\n    at Object.onReceiveStatus 
(/app/instrumentation.js:2:59254)\\n    at /app/instrumentation.js:2:145190\\n    at process.processTicksAndRejections 
(node:internal/process/task_queues:77:11)\\nfor call at\\n    at s.makeUnaryRequest (/app/instrumentation.js:2:63461)\\n    
at s.export (/app/instrumentation.js:2:130120)\\n    at t.send [as _send] (/app/instrumentation.js:2:569175)\\n    at 
/app/instrumentation.js:2:375395\\n    at new Promise (<anonymous>)\\n    at u._sendPromise 
(/app/instrumentation.js:2:375369)\\n    at u.send (/app/instrumentation.js:2:375741)\\n    at 
/app/instrumentation.js:2:363578\\n    at new Promise (<anonymous>)\\n    at e._export 
(/app/instrumentation.js:2:363513)\",\"message\":\"14 UNAVAILABLE: No connection 
established\",\"code\":\"14\",\"details\":\"No connection established\",\"metadata\":\"[object Object]\",\"name\":\"Error\"}". 
Log arguments are: []