### 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_
log_events = aws_client.logs.get_log_events(
                logGroupName=log_group_name, logStreamName=log_stream_name
            )["events"]
            return any(["starting wait" in e["message"] for e in log_events]) and any(
                ["done waiting" in e["message"] for e in log_events]
            )
        wait_until(_assert_log_output, strategy="linear")
    @pytest.mark.skipif(is_old_provider(), reason="old provider")
    @pytest.mark.xfail(reason="Currently flaky in CI")
    @markers.parity.aws_validated
    def test_lambda_invoke_timed_out_environment_reuse(
        self, create_lambda_function, snapshot, aws_client
    ):
        """Test checking if a timeout leads to a new environment with a new filesystem (and lost /tmp) or not"""
        regex = re.compile(r".*\s(?P<uuid>[-a-z0-9]+) Task timed out after \d.\d+ seconds")
        snapshot.add_transformer(
            KeyValueBasedTransformer(
                lambda k, v: regex.search(v).group("uuid") if k == "errorMessage" else None,
                "<timeout_error_msg>",
                replace_reference=False,
            )
        )
        func_name = f"test_lambda_{short_uid()}"
        create_result = create_lambda_function(
            func_name=func_name,
            handler_file=TEST_LAMBDA_TIMEOUT_ENV_PYTHON,