### Is there an existing issue for this?

- [X] I have searched the existing issues

### Feature description

I know this is a bit out there, and I'm probably the only one that wants this.

We're running a multi-tenanted localstack env, so we have multiple parent localstack containers running on the same host. Each parent container spawns child Lambda containers are required. With `LAMBDA_EXECUTOR: docker-reuse` at least, when a parent container spawns a child container it gives it the name:
`localstack_lambda_arn_aws_lambda_<region>_000000000000_function_<function_name>`.

The problem for us is that we cannot deploy a function with the same name across two localstack instances as the container names of the resulting Lambda containers overlap. If you do this and invoke the function, the container is created from the relevant parent - but then reused by all other parents as the container "already exists".

I'm not sure of the full implications of this, but at the very least it will use incorrect function code as it's just reusing the container created by the other instance. Presumably there is also issues RE: transparent SDK patching and DNS, as it's _probably_ talking to the wrong parent instance.

### 🧑‍💻 Implementation

I'm not sure what other implications this has, but I can see here that the Lambda container prefix is hard coded.
https://github.com/localstack/localstack/blob/49f36937c7d823f77ed821bfd4242e87d9685b7d/localstack/services/awslambda/lambda_executors.py#L1030 

Instead of the hard coded `localstack` value, could this instead use the localstack parent's container name?

If this causes an issue, could there perhaps be another environment variable added, allowing us to customise the Lambda container name prefix?

### Anything else?

_No response_
container_id, interactive=not background, attach=not background, stdin=stdin
            )
        else:
            mount_volumes = None
            if lambda_cwd:
                mount_volumes = [
                    (Util.get_host_path_for_path_in_docker(lambda_cwd), DOCKER_TASK_FOLDER)
                ]
            return DOCKER_CLIENT.run_container(
                image_name=docker_image,
                interactive=True,
                detach=background,
                entrypoint=entrypoint,
                remove=True,
                network=network,
                env_vars=env_vars,
                dns=dns,
                additional_flags=additional_flags,
                command=inv_context.lambda_command,
                mount_volumes=mount_volumes,
                stdin=stdin,
            )
class LambdaExecutorLocal(LambdaExecutor):
    def _execute_in_custom_runtime(
        self, cmd: Union[str, List[str]], lambda_function: LambdaFunction = None
    ) -> InvocationResult:
        """
        Generic run function for executing lambdas in custom runtimes.
        :param cmd: the command to execute
        :param lambda_function: function details