Provide actionable error messages when hitting socket sandbox limits

This issue is affecting some customers who have an application that opens sockets and is limited by the Sandbox when their Function is invoked in large numbers.

E.G

A Node.Js application that is using the Request Library for Node.Js to pass on the Request body to an MQTT endpoint.

A PHP Application that is creating a number of processes to handle the Function processing.

No source file, test, or entry point is named. Start by tracing how the host detects socket sandbox-limit failures, using the Node.js and PHP examples as reproduction contexts, then define what actionable error information should be exposed and add coverage for the resulting message.

Written by the indexing model from the issue text.