"Error: write EPIPE" on lambda errors (it worsens with provisioned concurrency)

## Prerequisites

* [x] I am running the latest version. (`up upgrade`)
* [X] I searched to see if the issue already exists.
* [X] I inspected the verbose debug output with the `-v, --verbose` flag.
* [X] Are you an Up Pro subscriber?

## Description
We have been using Up for our lambda solution (express server) for a while now (~2 years) and
we were seeing some errors like this (but not that frequently):
```
{"timestamp":1580983517551,"message":"ERROR\tUncaught Exception\t{\"errorType\":\"Error\",\"errorMessage\":\"write EPIPE\",\"code\":\"EPIPE\",\"errno\":\"EPIPE\",\"syscall\":\"write\",\"stack\":[\"Error: write EPIPE\",\" at WriteWrap.afterWrite [as oncomplete] (net.js:789:14)\"]}","extractedFields":{"event":"ERROR\tUncaught Exception\t{\"errorType\":\"Error\",\"errorMessage\":\"write EPIPE\",\"code\":\"EPIPE\",\"errno\":\"EPIPE\",\"syscall\":\"write\",\"stack\":[\"Error: write EPIPE\",\" at WriteWrap.afterWrite [as oncomplete]
```
to provide a bit more context, we also get an odd message coming almost an hour after this error shows up.

We decided to add provisioned concurrency and noticed that this error started happening more often.

Currently, this problem is producing 500 to some of our consumers.

## Steps to Reproduce

not sure I can describe this in a generic way but we see it quite often with or without provisioned concurrency.

## Love Up?
We are using Up pro currently.