### 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_
)
        snapshot.match("create-fn-response", create_response)
        response = aws_client.awslambda.get_function(FunctionName=function_name)
        snapshot.match("get-fn-response", response)
    @pytest.mark.skipif(
        is_old_provider(), reason="Credential injection not supported in old provider"
    )
    @markers.parity.aws_validated
    def test_lambda_different_iam_keys_environment(
        self, lambda_su_role, create_lambda_function, snapshot, aws_client
    ):
        """
        In this test we want to check if multiple lambda environments (= instances of hot functions) have
        different AWS access keys
        """
        function_name = f"fn-{short_uid()}"
        create_result = create_lambda_function(
            func_name=function_name,
            handler_file=TEST_LAMBDA_SLEEP_ENVIRONMENT,
            runtime=Runtime.python3_10,
            role=lambda_su_role,
        )
        snapshot.match("create-result", create_result)
        
        def _invoke_lambda(*args):
            result = aws_client.awslambda.invoke(
                FunctionName=function_name, Payload=to_bytes(json.dumps({"sleep": 2}))
            )
            return json.loads(to_str(result["Payload"].read()))["environment"]
        def _transform_to_key_dict(env: Dict[str, str]):