chore(release): 1.0.0-beta.7 [skip ci]

# [1.0.0-beta.7](https://git.gitlab.arm.com/bazel/toolchain_utils/compare/v1.0.0-beta.6...v1.0.0-beta.7) (2024-05-03)

### Bug Fixes

* **symlink/target:** add `files_to_run` property on `ToolchainInfo` provider ([2966744e](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/2966744e1328bef9143dbb5c9c1d32fc756e0219))
* **symlink/target:** add target to runfiles ([4ec23317](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/4ec23317cba14be99c3eec807e9b3873fc5636b0))
* **symlink/target:** merge all data runfiles ([753b43a4](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/753b43a44ff14e768dd98f9fd9234d4f30eb3d0d))
* **toolchain/test:** break `diff` loop correctly ([d57cc719](https://git.gitlab.arm.com/bazel/toolchain_utils/commit/d57cc71913ae936d26ed4a385ad3eb24bde6e8d9))

### BREAKING CHANGES

* **symlink/target:** `toolchain_symlink_path` no longer provides `ToolchainInfo`/`TemplateVariableInfo`.

It is required to use `toolchain_symlink_target` to the `toolchain_symlink_path`.

This is due to `toolchain_symlink_target` needing to export the `DefaultInfo.file_to_run` from the
symlinked target. That is not possible with a filesystem path.

This should not affect most users as `toolchain_symlink_path` is mainly used in `toolchain_local_which`.

If `toolchain_symlink_path` is being used, then to gain the previous functionality, create a
`toolchain_symlink_target` to the `toolchain_symlink_path` label.