Skip Developer ID checks when notarization is disabled

[afarchy]

Summary

• skip Developer ID identity discovery and validation when macOS notarization is disabled
• preserve Developer ID Application and Installer requirements for notarized, Steam, PKG, and DMG exports
• rebuild the committed action bundle

Problem

A non-App Store macOS export with notarize: false still runs security find-identity and fails unless a Developer ID Application certificate is installed. This makes non-notarized development/debugging exports require credentials that are only used by the notarization path.

Reproduction: https://github.com/virtual-maker-net/buildalon-web/actions/runs/33467584973

Validation

• npm ci
• npx tsc --noEmit
• npm run bundle

[afarchy]

Closing this fork-based PR because the validation workflow needs the head branch in this repository. I’ll reopen from an in-repository branch once write access is available.

[afarchy]

@RageAgainstThePixel I reopened this as a fork-based PR because I don't have write access to this repository, so I can't create the branch directly in the upstream repo. If Actions require an upstream branch, a maintainer will need to push or cherry-pick commit 7987f54 into one.

[StephenHodgson]

@afarchy you have access now

[afarchy]

Moved to in-repository branch codex/skip-developer-id-without-notarization and replaced by #36 now that write access is available.