feat: use electron-winstaller instead of self module

[beyondkmp]

1. Add customSquirrelExePath option, which allows using custom squirrel windows
2. Use official electron-winstaller
3. Support Windows ARM
4. Fix some bugs([Security] Hijacking DLL problem electron-builder-binaries#33, Squirrel.Windows does not support ARM64 electron-builder-binaries#52)

[changeset-bot]

🦋 Changeset detected

Latest commit: 11f53ee

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 8 packages

Name	Type
app-builder-lib	Patch
electron-builder-squirrel-windows	Patch
dmg-builder	Patch
electron-builder	Patch
electron-forge-maker-appimage	Patch
electron-forge-maker-nsis-web	Patch
electron-forge-maker-nsis	Patch
electron-forge-maker-snap	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[Stanzilla]

Is this package actually still supported by the electron team? Many packages in that org have been dead for a long time.

[mmaietta]

Is this package actually still supported by the electron team? Many packages in that org have been dead for a long time.

That's a great point. @beyondkmp what bug fixes is this solving for? (Can't tell from the description)

[mmaietta]

@Stanzilla looks like updates are still being pushed to electron-winstaller, last update was 3mo ago. https://www.npmjs.com/package/electron-winstaller

[beyondkmp]

@mmaietta Resolved the code conflict now, but this UT keeps failing, running locally is no problem. It looks like there is a problem with this UT on the master, help me out if you have time.

[mmaietta]

I'll take a look at this today. There is no problem on master though...as the commit test history is clean: https://github.com/electron-userland/electron-builder/commits/master/

[mmaietta]

I pushed your branch to origin/win-installer within the electron-builder repo and the tests all pass correctly: https://github.com/electron-userland/electron-builder/actions/runs/13076539224

My best guess is that running the job from your fork is not able to access that repo secret specifically?

[beyondkmp]

@mmaietta Yes, that's correct. The reason is the same as what you mentioned. The conflicts in this MR have been resolved. When you have time, please help review it again. If there are no issues, it can be merged.

[mmaietta]

Great work!