Update Bazel Dependencies

### What

It has been a while since Docs-as-Code bazel dependencies have been updated / upgraded.

We should look through and see what is the most recent releases of the things we use that we can import without breaking any downstream consumer or our own repo

### Acceptance Criteria (DoD)

Upgrade the bazel imports that are upgradeable without breaking anything downstream or internally.

Go one by one (if possible) to avoid issues with figuring out what caused the non functioning part.

### How

Go through `MODULE.bazel` and see what we can upgrade.

Example:

Current MODULE.bazel has:
`bazel_dep(name = "aspect_rules_py", version = "1.4.0")`

But newest version of aspect_rules_py is 2.2+, so this would be a candidate to try and see if we can upgrade.

Start with MODULE.bazel and inventory each current bazel_dep version, including aspect_rules_py at 1.4.0. Check newer releases one at a time, verifying that the repository and downstream consumers continue to work after each upgrade. Done means all safely upgradeable imports are updated without internal or downstream breakage.

Vom Indexierungsmodell aus dem Issue-Text verfasst.