### 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("put_fn_concurrency", put_fn_concurrency)
        aws_client.awslambda.invoke(
            FunctionName=fn_arn, InvocationType="Event", Payload=json.dumps({"wait": 10})
        )
        aws_client.awslambda.invoke(
            FunctionName=fn_arn, InvocationType="Event", Payload=json.dumps({"wait": 10})
        )
        time.sleep(4)  # make sure one is already in the "queue" and one is being executed
        with pytest.raises(aws_client.awslambda.exceptions.TooManyRequestsException) as e:
            aws_client.awslambda.invoke(FunctionName=fn_arn, InvocationType="RequestResponse")
        snapshot.match("too_many_requests_exc", e.value.response)
        with pytest.raises(aws_client.awslambda.exceptions.InvalidParameterValueException) as e:
            aws_client.awslambda.put_function_concurrency(
                FunctionName=fn_arn, ReservedConcurrentExecutions=2
            )
        snapshot.match("put_function_concurrency_qualified_arn_exc", e.value.response)
        aws_client.awslambda.put_function_concurrency(
            FunctionName=func_name, ReservedConcurrentExecutions=2
        )
        aws_client.awslambda.invoke(FunctionName=fn_arn, InvocationType="RequestResponse")
        def assert_events():
            log_events = aws_client.logs.filter_log_events(
                logGroupName=f"/aws/lambda/{func_name}",
            )["events"]
            assert len([e["message"] for e in log_events if e["message"].startswith("REPORT")]) == 3
        retry(assert_events, retries=120, sleep=2)
        # TODO: snapshot logs & request ID for correlation after request id gets propagated
        #  https://github.com/localstack/localstack/pull/7874
    @markers.parity.aws_validated
    def test_reserved_concurrency(