Idan Saadon authored Aug 13, 2024 and Matthew Clarkson committed Aug 13, 2024

The previous target results in a `labgrid` import which conflicts with upstream `labgrid` module.

This refactor means that the custom manager executor library is imported with `bazel.labgrid.executor`.

BREAKING CHANGE: `@rules_labgrid//labgrid/executor:manager` is now `@rules_labgrid//bazel/labgrid/executor`

```
cd e2e
bazelisk test remote:test
```

Provides `@ape//ape/toolchain/info:*` targets plus makes
`@ape//ape:*` targets publically visible.

Enabled by default in Bazel 6.

This removes complexity in the context manager. It consolidates the control
of the execution into the executor.

BREAKING CHANGE: LabGrid context managers now return `labgrid.manager#Data` rather than `Run` functions.

> If you use zsh and have trouble running APE programs try `sh -c ./prog`
> or simply upgrade to zsh 5.9+ (since we patched it two years ago).
> The same is the case for Python subprocess, old versions of fish, etc.

https://github.com/jart/cosmopolitan?tab=readme-ov-file#shells

Allows creating executor targets easily.

Provides multi-platform transitions for `labgrid_genrule` and friends.

This can be used directly as a target, there is no need for
a toolchain for this.

Loads a Python context manager to set up the LabGrid environment
before running the provided binary.

Will be used for hermetic binaries.

Will be used to provide a binary that runs on the host.

Provides a `py_binary` that can run a command under the `DockerDriver`.

This is _not_ hermetic but provides a useful example of
how the LabGrid API can be used.

Allows downstream packages to include the `labgrid` Python module
into their tests.

Needed for `DockerDriver`