ci(app): electron builder Windows signing workaround

[y3rsh]

Overview

There’s an issue in Electron Builder/TrustedSigning that causes an error when installing the required tooling for code signing. Windows signing fails. I don't know how the build I did against edge PR ever even worked.
electron-userland/electron-builder#9076

@y3rsh is ok with this pain using a beta and does not want to fall back to using DigiCert. BUT it will require diligence.

Solution

The work around comes from
electron-userland/electron-builder#9076 (comment)

1. Before the electron builder runs, install TrustedSigning at the specific version Electron Builder wants
2. Invoke this tool on a single dummy.exe just like Electron Builder will be invoking it on our files.
3. The dependencies needed for this type of signing are automatically installed.
4. The signing fails as expected but all the tools for signing are ready for electron builder in the next step, sidestepping the issue.

Test Plan and Hands on Testing

• Successful build and sign using the work around https://github.com/Opentrons/opentrons/actions/runs/15357038874/job/43218143087
• Add a comment in the Workflow

Review requests

I considered directly trying to install the dependencies... but I think it seems best to leave that to TrustedSigning. So the invoke is necessary.

        Build tools package installed: False
	Trusted signing package installed: False
	Sign CLI package installed: False
	Installing required dependencies.
		Found existing package source: https://www.nuget.org/api/v2/
		Installing package: Microsoft.Windows.SDK.BuildTools 10.0.22621.3233
		Installing package: Microsoft.Trusted.Signing.Client 1.0.53
		Installing package: sign 0.9.1-beta.2[44]

[mjhuff]

Makes sense to me. Hopefully it's smooth sailing ⛵