feat: Add @electron/windows-sign

[felixrieseberg]

• I have read the contribution documentation for this project.
• I agree to follow the code of conduct that this project follows, as appropriate.
• The changes are appropriately documented (if applicable).
• The changes have sufficient test coverage (if applicable).
• The testsuite passes successfully on my local machine (if applicable).

Summarize your changes:

This PR adds @electron/windows-sign, enabling this module to codesign Windows binary files. Both logic and configuration are analogous to @electron/osx-sign -- on purpose, to keep the API simple and easy to use.

[MarshallOfSound]

Is this definitely run after the afterCopy hook? Just double checking this is run after any potential mutations to the exe. E.g. via fuses

[felixrieseberg]

Yep! The only thing that happens after is moving the package to its final destination and the afterComplete hook. For future convenience, this is also exactly when we sign & notarize on macOS.

[continuous-auth]

🎉 This PR is included in version 18.1.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[savely-krasovsky]

@felixrieseberg how exactly I should use it? I tried object with just signWithParams (we use cert from system storage), but it throws path-related error. I tried to specify appDirectory, it goes further but there are no binary at this moment yet (they are in some packager temporary dir).

UPD:
Fixed it with config like this, but it seems for me counter-intuitive.

windowsSign: {
  appDirectory: process.env.LOCALAPPDATA + "\\Temp\\electron-packager",
  signWithParams: "/sha1 certhash"
}