## 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.
super(LambdaExecutorSeparateContainers, self).__init__()
        self.max_port = LAMBDA_API_UNIQUE_PORTS
        self.port_offset = LAMBDA_API_PORT_OFFSET
    def prepare_event(self, environment: Dict, event_body: str) -> bytes:
        
        environment["DOCKER_LAMBDA_USE_STDIN"] = "1"
        return event_body.encode()
    def execute_in_container(
        self,
        lambda_function: LambdaFunction,
        inv_context: InvocationContext,
        stdin=None,
        background=False,
    ) -> Tuple[bytes, bytes]:
        docker_image = Util.docker_image_for_lambda(lambda_function)
        container_config = LambdaContainerConfiguration(image_name=docker_image)
        container_config.env_vars = inv_context.environment
        if inv_context.lambda_command:
            container_config.entrypoint = ""
        elif inv_context.handler:
            inv_context.lambda_command = inv_context.handler
        
        container_config.network = get_container_network_for_lambda()
        if container_config.network == "host":
            port = get_free_tcp_port()