fix(lambda): increase socket and HTTP timeout for Lambda extension

It turns out that 100 ms is sometimes not enough, although
communication to the Lambda extension happens on localhost. If the
extension is up and runnig but communication between the Node.js
in-process collector and the extension fails at some point, the
Node.js in-process collector will stop attempting to talk to the
extension. Consequently, the extension will wait to receive the Lambda
entry span, which will never happen, causing the Lambda invocation to
run into a timeout.

packages/serverless/src/backend_connector.js

@@ -18,7 +18,7 @@ let useLambdaExtension = false;
 
 const timeoutEnvVar = 'INSTANA_TIMEOUT';
 let defaultTimeout = 500;
-const layerExtensionTimeout = 100;
+const layerExtensionTimeout = 300;
 let backendTimeout = defaultTimeout;
 
 const proxyEnvVar = 'INSTANA_ENDPOINT_PROXY';