chore: remove unneeded electron-builder flags

Drop the electronFuses block and verifyUpdateCodeSignature: false added
in #3740. Neither is required for the ssh2 tunnel to work:

- ssh2's native bindings (sshcrypto.node, cpufeatures.node) are
  auto-unpacked by Electron and don't conflict with default fuses.
- onlyLoadAppFromAsar only governs the entry point (main.js), which
  stays inside the asar.
- Embedded asar integrity validation is handled correctly by modern
  electron-builder, including for asarUnpack entries.
- verifyUpdateCodeSignature only matters when electron-updater is
  active; Keira3 doesn't ship the auto-updater.

signAndEditExecutable stays false until a Windows code-signing
certificate is available.

Author: Helias

electron-builder.json

@@ -5,15 +5,10 @@
     "output": "release/"
   },
   "files": ["dist/browser/**/*", "main.js", "main.js.map"],
-  "electronFuses": {
-    "enableEmbeddedAsarIntegrityValidation": false,
-    "onlyLoadAppFromAsar": false
-  },
   "win": {
     "icon": "dist/browser",
     "target": ["portable"],
-    "signAndEditExecutable": false,
-    "verifyUpdateCodeSignature": false
+    "signAndEditExecutable": false
   },
   "mac": {
     "icon": "dist/browser",