[NOTICE] Pin to old debian version if seeing issues with debian 12 (bookworm)

[Debian 12 bookworm](https://www.debian.org/releases/bookworm/) was released on June 10th, 2023. As of June 15th, 2023, many of the images we publish in [`devcontainers/images`](https://github.com/devcontainers/images) have also been updated to use bookworm as a base. We have tagged these `bookworm` based images with a new major version and continue to tag alternative versions with older debian OSs (eg bullseye).

As with any major OS release, it takes time for upstream dependencies that these Features rely on to update. Notably, several Features in this repo rely on the debian apt repositories maintained by Microsoft, which has only just started to [get populated](https://packages.microsoft.com/repos/microsoft-debian-bookworm-prod/).

**If you're seeing a new install failure related to debian bookworm, please pin your dev container's base image to the previous version of debian. An example is shown below:**.

For example, for [`typescript-node`](https://github.com/devcontainers/images/tree/main/src/typescript-node), using an image tag that references `-bullseye` (the previous version of Debian) works:

```jsonc
{
"image": "mcr.microsoft.com/devcontainers/typescript-node:1-16-bullseye", // bullseye is version 11 of Debian
"features": {
"ghcr.io/devcontainers/features/docker-in-docker:2": {}
}
}
```

All the tags for a given image can be found from the README on the `devcontainers/images` repo (eg: https://mcr.microsoft.com/v2/devcontainers/typescript-node/tags/list)

Alternatively, pinning to the previous major version is another possible strategy (`mcr.microsoft.com/devcontainers/typescript-node:0-16`)

Please bear with us as we work to update everything in our control and harden where we are forced to wait! **The best practice here is to always pin images in your dev containers to a specific distro/version to avoid any impact in the future**.

Related:
https://github.com/devcontainers/images/issues/607
https://github.com/devcontainers/features/issues/573
https://github.com/devcontainers/images/pull/630
https://github.com/devcontainers/images/pull/608

Beginne mit dem Hinweistext und der dort verlinkten README von devcontainers/images und prüfe die Debian-Image-Tags bookworm und bullseye sowie die zugehörigen Issues und Pull Requests. Erledigt ist die Aufgabe, wenn die Anleitung weiterhin korrekt ist und klar erklärt, wie eine frühere Distribution oder eine frühere Major-Version des Images festgelegt werden kann; es wird keine Quelldatei oder kein Test angegeben.

Vom Indexierungsmodell aus dem Issue-Text verfasst.