### Is there an existing issue for this?

- [X] I have searched the existing issues

### Enhancement description

Hi, can we add the new lambda docker repos to  [the list](https://github.com/localstack/localstack/blob/800c54e29231caf5fcd78d5be52a55cb1fe4f453/localstack/utils/diagnose.py#L16)?

It seems like we are missing the new nodejs16/18, python 3.9/3.10, java 17, dotnet6 and the new repository. `public.ecr.aws/`.

Current list:
```
 "docker-dependent-image-hashes": {
        "localstack/lambda:provided": "not_present",
        "localstack/lambda:ruby2.7": "not_present",
        "localstack/lambda:nodejs14.x": "not_present",
        "localstack/lambda:nodejs12.x": "not_present",
        "localstack/lambda:java8": "not_present",
        "localstack/lambda:java11": "not_present",
        "localstack/lambda:go1.x": "not_present",
        "localstack/lambda:dotnetcore3.1": "not_present",
        "localstack/lambda:python2.7": "not_present",
        "localstack/lambda:python3.6": "not_present",
        "localstack/lambda:python3.7": "not_present",
        "localstack/lambda:python3.8": "not_present",
        "localstack/bigdata": "not_present",
        "lambci/lambda:provided": "not_present",
        "lambci/lambda:ruby2.7": "not_present",
        "lambci/lambda:nodejs14.x": "not_present",
        "lambci/lambda:nodejs12.x": "not_present",
        "lambci/lambda:java8": "not_present",
        "lambci/lambda:java11": "not_present",
        "lambci/lambda:go1.x": "not_present",
        "lambci/lambda:dotnetcore3.1": "not_present",
        "lambci/lambda:dotnetcore2.1": "not_present",
        "lambci/lambda:dotnetcore2.0": "not_present",
        "lambci/lambda:python2.7": "not_present",
        "lambci/lambda:python3.6": "not_present",
        "lambci/lambda:python3.7": "not_present",
        "lambci/lambda:python3.8": "not_present",
        "mongo": "not_present"
    },
```

### 🧑‍💻 Implementation

_No response_

### Anything else?

_No response_
def test_provisioned_concurrency(self, create_lambda_function, snapshot, aws_client):
        """
        TODO: what happens with running invocations in provisioned environments when the provisioned concurrency is deleted?
        TODO: are the previous provisioned environments not available for new invocations anymore?
        TODO: lambda_client.delete_provisioned_concurrency_config()
        Findings (mostly through manual testing, observing, changing the test here and doing semi-manual runs)
        - execution environments are provisioned nearly in parallel (we had *ONE*  case where it first spawned 19/20)
        - it generates 2x provisioned concurrency cloudwatch logstreams with only INIT_START
        - updates while IN_PROGRESS are allowed and overwrite the previous config
        """
        func_name = f"test_lambda_{short_uid()}"
        create_lambda_function(
            func_name=func_name,
            handler_file=TEST_LAMBDA_INVOCATION_TYPE,
            runtime=Runtime.python3_10,
            client=aws_client.awslambda,
        )
        v1 = aws_client.awslambda.publish_version(FunctionName=func_name)
        put_provisioned = aws_client.awslambda.put_provisioned_concurrency_config(
            FunctionName=func_name, Qualifier=v1["Version"], ProvisionedConcurrentExecutions=5
        )
        snapshot.match("put_provisioned_5", put_provisioned)
        get_provisioned_prewait = aws_client.awslambda.get_provisioned_concurrency_config(
            FunctionName=func_name, Qualifier=v1["Version"]
        )
        snapshot.match("get_provisioned_prewait", get_provisioned_prewait)
        assert wait_until(concurrency_update_done(aws_client.awslambda, func_name, v1["Version"]))
        get_provisioned_postwait = aws_client.awslambda.get_provisioned_concurrency_config(
            FunctionName=func_name, Qualifier=v1["Version"]
        )