visualization_install_tests vs macOS python3.12 upgrade

[jwnimmer-tri]

The visualization_install_tests are somewhat brittle w.r.t. how we choose macOS python versions.

For now, I'm going to disable them on macOS to unbreak CI.

The problem is that the installed programs use the shebang line #!/usr/bin/env python3, which in Unprovisioned macOS builds is not /opt/homebrew/bin/python3.11 but something else ... maybe Apple Python? Anyway, it doesn't work.

Probably to fix these tests, we need to set a $PATH with a magic symlink to sys.executable.

[jwnimmer-tri]

@mwoehlke-kitware with the venv, I believe we can probably revert the #21024 now. Could you give it a try?

CC @BetsyMcPhail

[nicolecheetham]

The mac job for the PR made to revert this one fails. Therefore it will be closed.
PR link: #22174

[jwnimmer-tri]

It doesn't make any sense why Provisioned and Unprovisioned jobs would have a different result. That needs some investigation.

[BetsyMcPhail]

Provisioned (passed): https://drake-jenkins.csail.mit.edu/view/Pull%20Request/job/mac-arm-sonoma-clang-bazel-experimental-release/683/
Unprovisioned (failed): https://drake-jenkins.csail.mit.edu/view/Mac%20Sonoma%20Unprovisioned/job/mac-arm-sonoma-unprovisioned-clang-bazel-experimental-release/53/

[jwnimmer-tri]

It doesn't make any sense why Provisioned and Unprovisioned jobs would have a different result. That needs some investigation.

Specifically, the PR does not change any setup/... code, it only runs a couple of extra test cases. Having different CI results for Provisioned and Unprovisioned in the absence of setup changes indicates that the current Provisioned image snapshot has somehow diverged from what would happen if we were to make a new snapshot today.

It may very well be that this issue is still unfixed and the test cases are true positive failures, indicating that we need further changes to our code. However, we should first understand why the provisioned snapshot seems to be inauthentic, before proceeding further.

[nicolecheetham]

In both of the unprovisioned job attempts there was a failure with //:py/install_test. In addition they mention a failed result of
pydrake/visualization/test/visualization_install_tests.py. However, in both provisioned jobs there is no mention of running pydrake/visualization/test/visualization_install_tests.py let alone fail.