Python Environment Tools binaries can't build on macOS

[jmcphers]

It is currently not possible to turn another build of the Python Environment Tools because it can't build on macOS. The macOS Github Actions runners do not take jobs from public repositories, and now that the positron-pet-builds repository is public, it cannot run jobs on these runners.

This means that if you attempt to build the PET repo, it will hang at the macOS build step waiting for a runner that will never be available.

This problem must be resolved before we can take another release of the Python Environment Tools

Possible fixes:

• when we need to take another build of the tools (which isn't that often), temporarily make the runners public, perform the build, then switch them back to private
• make the repository private again and require a github access token to download the binaries (as we did for other private repositories)
• split it into two repositories, one private repository that performs the build and one public repository that hosts the binary build artifacts as releases (this is what we do for e.g. Kallichore)
• run away from home and live in the woods

[isabelizimm]

I would prefer to not require special credentials to get a dev build up, and switching things between private and public seems like a nuisance long term.

split it into two repositories, one private repository that performs the build and one public repository that hosts the binary build artifacts as releases (this is what we do for e.g. Kallichore)

Seems like the cleanest option. The private repo will be pretty minimal, but the overall process feels smoother (and aligns with prior art).

[petetronic]

Note this was the intent for python-environment-tools in https://github.com/posit-dev/positron-builds. If we really need a separate private repo, that's fine, but let me know and we'll clean up positron-builds repo to not expect to build this.