These have been deprecated for a few releases and were badly
named. These targets are now under `@ape//ape/toolchain/info:*` targets. `@ape//ape:*` targets are `exec`/`target` configuration flexible.

Allows downstream users to select a `target` configuration
compatible APE target.

The `@ape//:*` targets are explicitly for the `exec` configuration.

This has lead to confusion when selecting a APE binary target that is needed
for the `target` configuration.

New `@ape//ape/toolchain/info` targets have been added to make the target name
explicit. A toolchain will _always_ be for the execution platform.

This rule only depends on local data so can be marked as such.

If a Linux user has Wine installed with the `binfmt_misc` registration,
an APE binary is picked up and ran under the Wine runtime.

Normally, this does not occur, as we force execution under the launcher.

However, Python `sys.executable` will return the original binary so
any Python script that uses `sys.executable` with `subprocess` will
unexpectedly run under Wine.

Assimilating the binary on Linux avoids this situation. In all other cases
we can symlink to the binary.

This tags targets which cannot build on every platform and
run targets that are unnecessary to build as part of a
recursive build.

We need to make sure our APE binary targets work when symlinked.

The shift to assimilated binaries removes the need for runfiles.

The test will pass with assimilated binary targets.

Assimilated binaries are not runnable on Apple Silicon and require
the APE loader.

Symlinking the "fat" APE will force the loader to be extracted to
run the binary.

Targets have been created for both `ape_binary` and `ape_assimilate`
so that we can `select`, if we want to.

BREAKING CHANGE: The `ape_binary#target` attribute has changed to `ape_binary#src`.

This aligns to other `*_binary` rules such as `sh_binary`.

Assimilated binaries are converted from a "fat" APE into a native
binary for the provided host.

This change means that the APE binaries are completely hermetic
binaries that do not require their own launcher, shell script or
anything else.

This solves a huge bootstrapping problem that POSIX shell scripts
need runfiles but to effectively find the runfiles one needs POSIX
tooling to resolve symlinks, etc.

Having a single executable to rely on solves the need for runfiles.

This rule takes a APE binary and turns it into a native binary.

This can be used to convert a APE into a native binary

Fixes hermeticity and runfiles issues with `curl`.

Thomas Wilks authored May 21, 2024 and Matthew Clarkson committed May 22, 2024

`pigz` is being downgraded because with the current version decompression
fails[1]:

```sh
$ curl -sLf https://github.com/ahgamut/superconfigure/releases/download/z0.0.39/compress.zip -o compress.zip
$ unzip compress.zip
$ echo "Hello, world" > hello-world.txt
$ ./bin/pigz hello-world.txt
$ ./bin/pigz -cdkv hello-world.txt.gz --stdout > hello-world.txt~
(segmentation fault)
```

The `3.2.4` binary worked fine, so we are rolling back to that for now.

When a new version of `cosmos` binaries have been released, we should
check that the decompression works and upgrade.

[1]: https://github.com/ahgamut/superconfigure/issues/38

There have been no changes between `3.3.1` and `3.3.3` so the integrity
is identical.