### Is there an existing issue for this?

- [X] I have searched the existing issues

### Feature description

The use case I have in mind is to run Node 16.x Lambdas - the default container registry is `lambci/lambda` which is effectively abandoned. [Not even Node 14.x has been published](https://github.com/lambci/docker-lambda/pull/330). However, switching the registry over to [`amazon/aws-lambda-nodejs`](https://hub.docker.com/r/amazon/aws-lambda-nodejs) still fails to pull the container, since localstack is looking for the tag `nodejs16.x`. I'd like to be able to specify that if the runtime is `nodejs16.x` it just looks for tag `16`.

### 🧑‍💻 Implementation

_No response_

### Anything else?

_No response_
func_arn: str,  
        lambda_function: LambdaFunction,
        event: Dict,
        context: LambdaContext = None,
        version: str = None,
        asynchronous: bool = False,
        callback: Callable = None,
        lock_discriminator: str = None,
    ):
        
        from localstack.utils.aws.message_forwarding import lambda_result_to_destination
        def do_execute(*args):
            @cloudwatched("lambda")
            def _run(func_arn=None):
                with contextlib.ExitStack() as stack:
                    if lock_discriminator:
                        stack.enter_context(LAMBDA_ASYNC_LOCKS.locks[lock_discriminator])
                    
                    invocation_time = int(time.time() * 1000)
                    
                    raised_error = None
                    result = None
                    dlq_sent = None
                    invocation_type = "Event" if asynchronous else "RequestResponse"
                    inv_context = InvocationContext(
                        lambda_function,
                        event=event,
                        function_version=version,
                        context=context,
                        invocation_type=invocation_type,