### 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_name=func_name,
            handler_file=lambda_fn,
            runtime=lambda_runtime,
            client=lambda_client,
        )
        result = lambda_client.invoke(FunctionName=func_name)
        result_data = result["Payload"].read()
        assert result["StatusCode"] == 200
        assert json.loads(result_data)["counter"] == 0
        result = lambda_client.invoke(FunctionName=func_name)
        result_data = result["Payload"].read()
        assert result["StatusCode"] == 200
        assert json.loads(result_data)["counter"] == 1
    @pytest.mark.parametrize(
        ["lambda_fn", "lambda_runtime"],
        [
            (TEST_LAMBDA_TIMEOUT_PYTHON, LAMBDA_RUNTIME_PYTHON38),
        ],
        ids=["python"],
    )
    @pytest.mark.xfail(
        os.environ.get("TEST_TARGET") != "AWS_CLOUD",
        reason="lambda timeouts not supported currently",
    )  
    def test_lambda_timeout_logs(
        self,
        lambda_client,
        create_lambda_function,
        lambda_fn,
        lambda_runtime,