Evaluate the best extraction method for repository rules

Alternatives:
* What we have in legacy - Python interpreter + `installer` whl
* What we have in pipstar - `repository_ctx.extract` + `chmod` and `repository_ctx.rename`
* What `uv` is using - https://github.com/astral-sh/uv/blob/0.9.28/crates/uv-extract/src/sync.rs
* A regular `uutils` chmod + unzip

For the last thing we would probably have to setup:
- development rust toolchain.
- binary archiving as part of release. We could probably download the right thing and store hashes using the new `facts` API for `bzlmod`.
- download the binary as a dependency to `whl_library`.

This is a followup to #3554 and #3555.

先阅读 follow-ups #3554 和 #3555，然后比较 legacy Python interpreter 和 installer wheel 的路径、pipstar 的 repository_ctx.extract/chmod/rename 路径、uv's crates/uv-extract/src/sync.rs，以及 uutils 的 chmod/unzip 选项。检查 issue 中描述的 release、whl_library 和 bzlmod 对 facts API 的影响。完成的标准是选择并记录一种有充分依据的 extraction 方案，以及该方案对 toolchain、dependency、binary-release 和 hash 的要求。

由索引模型根据 Issue 内容生成。