Missing signature for darwin-arm64 pet binary

[disenchant]

The pet binary for darwin-arm64 is not signed which makes it hard to allowlist with tools like Santa.

$ codesign -dv ~/.vscode/extensions/ms-python.vscode-python-envs-1.36.0-darwin-arm64/python-env-tools/bin/pet
Executable=/Users/[username]/.vscode/extensions/ms-python.vscode-python-envs-1.36.0-darwin-arm64/python-env-tools/bin/pet
Identifier=pet-2bba45dba123fe6f
Format=Mach-O thin (arm64)
CodeDirectory v=20400 size=43949 flags=0x20002(adhoc,linker-signed) hashes=1370+0 location=embedded
Signature=adhoc
Info.plist=not bound
TeamIdentifier=not set
Sealed Resources=none
Internal requirements=none

Related Issues / PRs:

• Fix issues with localization and signing vscode-python#23931
• Binary not signed python-environment-tools#139

[eleanorjboyd]

Raymond Zhao (@rzhao271) hm came up again but different OS type now

[mohityadav8]

Raymond Zhao (@rzhao271) can i work on this

[eleanorjboyd]

🤖 Triage: the ad-hoc signature on the packaged darwin-arm64 PET binary is a real allowlisting problem, but a fix needs a release/signing plan rather than a code change in interpreter discovery. We should decide who signs the distributed binary (PET build versus extension packaging), which identity and CI credentials to use, and how to verify the signature in the published VSIX. Marking this packaging debt as needs proposal.