Evaluate the best extraction method for repository rules

[aignas]

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.

[aignas]

To add, it seems that pip is chmoding the output files if they are marked executable, so in this case pipstar indeed introduces a regression, where without chmoding we are not creating the right output.

Source: https://github.com/pypa/pip/blob/3898741e29b7279e7bffe044ecfbe20f6a438b1e/src/pip/_internal/utils/unpacking.py#L88-L100

This I got from reading the source code of uv_extract.

[aignas]

And rules_js is using bsd_tar toolchain from tar.bzl:
https://github.com/aspect-build/rules_js/blob/main/npm/private/npm_import.bzl#L564

[aignas]

Related: #3091