It makes more sense to have the specific attribute for the concrete
rule rather than in the library function

On Windows `ctx.symlink` actually creates hardlinks.

BREAKING CHANGE: `symlinks` in the rule is now `links`

```diff
 download_archive(
-    symlinks = {
+    links = {
         "abc.txt": "def.txt",
     }
 )
```

We can use `symlinks` now.

Allows creating symlinks in the created download repositories.

This is especially useful for cross-platform creation of symlinks.

When a tool such as `//abc.sh` is provide. In nested projects it
was being resolved to the full label with the workspace.

This patch checks if the workspace is the same as the provided label,
if so do not add the workspace.

`use_repo_rule` never made it into Bazel 6.4.0

Individual `defs.bzl` files allow a fine-grained load graph for
Bazel so it only has to load `.bzl` files that it needs to.

This is much better than a single `defs.bzl` that pulls in all
the different `load` statements.

`rules_toolchain` is now open-source 🎉

Install them directly from GitLab

Double down on all hermetic tooling should be provided in `tools`.

`rules_coreutils` should be the ruleset that provides hermetic coreutils,
not `rules_download`.

Users should only pay for what they use and if they never use core utilities,
we download it everytime.