The project was originally named `rules_toolchain`.

After bikeshedding for the Bazel Central Registry (BCR),
`toolchain_utils` was deemed a better name.

Splitting out `resolved`/`which` repository rules makes sense.

It prevents any missing tools from raising an error in the toolchain resolution
rather than later via the stub.

This is _much_ more **user** friendly.

Including the `resolved` target in the local repository was more
**developer** friendly as it negated the need for two repositories.

We want to be **user** friendly.

Allows the `load` graph to be "load what you use" rather than pulling
in all `.bzl` files in a single `def.bzl` file.

This removes the need for a custom `resolved` rule for every toolchain.

Upgrade path is to add the `toolchain_type` to the local repository
rule in `MODULE.bazel` and change the `resolved` target to an alias.

A `toolchain_resolved` repository rule is added as well for toolchains
that do not use local binaries.

This patch hugely simplifies the creation of toolchains downstream.