### 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_
assert wait_until(
            concurrency_update_done(aws_client.awslambda, func_name, alias_name),
            strategy="linear",
            wait=30,
            max_retries=20,
            _max_wait=600,
        )  # this is SLOW (~6-8 min)
        # concurrency should still only work for the alias now
        # NOTE: the old version has been de-provisioned and will run 'on-demand' now!
        assert (
            get_invoke_init_type(aws_client.awslambda, func_name, first_ver["Version"])
            == "on-demand"
        )
        assert (
            get_invoke_init_type(aws_client.awslambda, func_name, new_version["Version"])
            == "provisioned-concurrency"
        )
        assert (
            get_invoke_init_type(aws_client.awslambda, func_name, alias_name)
            == "provisioned-concurrency"
        )
        # ProvisionedConcurrencyConfig should only be "registered" to the alias, not the referenced version
        with pytest.raises(
            aws_client.awslambda.exceptions.ProvisionedConcurrencyConfigNotFoundException
        ) as e:
            aws_client.awslambda.get_provisioned_concurrency_config(
                FunctionName=func_name, Qualifier=new_version["Version"]
            )
        snapshot.match("provisioned_concurrency_notfound", e.value.response)
    @markers.parity.aws_validated