## Problem
Currently, even if `LAMBDA_REMOTE_DOCKER=1`, we unzip the zip files in the directory they are in, which is usually /var/lib/localstack, which usually has a bind mount to the host.
On docker desktop, due to the use of grpc-FUSE (on macos), this can be very slow, about 200 times slower than on volumes / directly on the host. With experimental virtio filesystem enabled (also on macos), this can be reduced to about 30 times as slow, but still problematic.
This means a lambda may take a lot of time processing, for each additional layer some more. This especially affects nodejs lambdas with huge node_modules folders.

## Probable solution
At least if `LAMBDA_REMOTE_DOCKER=1`, we should leave the initial zip files on the bind mount (for persistence etc), but the working directories after unzipping should be located on non-bind mounts, to speed up the IO for unzipping.
self._stdout = stdout
        self._stderr = stderr
    def stderr_formatted(self, truncated_to: int = config.LAMBDA_TRUNCATE_STDOUT):
        return truncate(to_str(self._stderr).strip().replace("\n", "\n> "), truncated_to)
    def stdout_formatted(self, truncated_to: int = config.LAMBDA_TRUNCATE_STDOUT):
        return truncate(to_str(self._stdout).strip(), truncated_to)
    def output_file(self):
        try:
            with tempfile.NamedTemporaryFile(
                dir=config.dirs.tmp, delete=False, suffix=".log", prefix="lambda_"
            ) as f:
                LOG.info(f"writing log to file '{f.name}'")
                f.write(to_bytes(self._stderr))
        except Exception as e:
            LOG.warning("failed to write log to file, error %s", e)
EXECUTOR_LOCAL = LambdaExecutorLocal()
EXECUTOR_CONTAINERS_SEPARATE = LambdaExecutorSeparateContainers()
EXECUTOR_CONTAINERS_REUSE = LambdaExecutorReuseContainers()
DEFAULT_EXECUTOR = EXECUTOR_CONTAINERS_SEPARATE
AVAILABLE_EXECUTORS = {
    "local": EXECUTOR_LOCAL,
    "docker": EXECUTOR_CONTAINERS_SEPARATE,
    "docker-reuse": EXECUTOR_CONTAINERS_REUSE,
}