Bump browserslist from 4.17.0 to 4.29.0 in /app - #1407

- Replace deprecated Electron remote usage with @electron/remote
- Add shared wrappers for remote access and electron-store
- Upgrade Electron and electron-rebuild

- Update Electron runtime and lockfile
- Note `yarn test` in AGENTS.md

- Guard QR generation when transaction data is missing
- Add Electron and Ledger transport mocks for Jest
- Fall back to in-memory store outside Electron

- Bump the Electron runtime and related lockfile dependencies
- Refresh transitive packages for the newer Electron toolchain

- Bump Electron runtime from 22.3.27 to 28.3.3
- Refresh matching Node type and lockfile entries

- Bump Electron to 34.5.8
- Launch main dev script through a wrapper and guard process.mainModule

- Bump Electron runtime and refresh lockfile dependencies

- Bump Electron runtime from 40.10.5
- Refresh lockfile for the new Electron release

Migrates config to the v26 schema: linux.desktop entries nest under
`entry`, and win.publisherName moves into signtoolOptions. Drops the
dead greymass.pfx reference.

Windows packaging can no longer be cross-compiled from macOS —
@electron/rebuild does not support node-hid's pkg-prebuilds binaries.
Documented in AGENTS.md.

`@ledgerhq/hw-transport-node-hid@6.6.0` is TypeScript-compiled to ES5 and
inherits via the `__extends` helper, whose generated constructor calls
`_super.apply(this, arguments)`. It declares its base class as
`@ledgerhq/hw-transport-node-hid-noevents@^6.6.0`, and that caret range had
floated to 6.35.4, which ships a native ES6 `class`. Invoking an ES6 class
via `.apply()` throws, so every connection attempt failed with:

    TypeError: Class constructor TransportNodeHidNoEvents
    cannot be invoked without 'new'

This regressed in 77819d0, which added the node-hid/usb resolutions and
regenerated app/yarn.lock; the base class drifted as a side effect. Ledger
has been broken on this branch since, on all platforms.

The failure also leaked HID handles. `TransportNodeHid.open()` evaluates
`new HID(path)` as an argument before the constructor that throws, so the
opened device was orphaned with no reference and no close(). The leaked
handle blocked the next retry with "cannot open device" until GC reclaimed
it, producing an endless alternation between the two errors.

Upgrade the transport to 6.33.5 so both sides of the inheritance are ES6.
This requires moving the `usb` resolution from 1.7.2 to 2.9.0: 6.33.5's
listenDevices.js uses the usb 2.x named-export API (`usb.usb.on("attach")`),
which does not exist in 1.7.2 where the module *is* the binding. usb 2.9.0
also ships N-API prebuilds for win32-x64 and win32-ia32, removing the
per-arch source compile and surviving future Electron upgrades.

Bound the reconnect loop so a persistent failure no longer retries forever
and keeps the device busy. A renderer-initiated request resets the budget.
Also align before-quit on clearTimeout, matching the setTimeout handle.

Verified on Windows against a Nano X: transport opens and transactions sign.

The suite was written in 2019 and enforced by CircleCI until the npm to yarn
migration broke that config, which then went unnoticed for years. By now 55 of
the 61 files only asserted that components rendered exactly as they did in 2019,
and Jest 24 could no longer parse its own dependencies, so nothing had run in a
long time.

Drops jest, enzyme, react-test-renderer and eslint-plugin-jest along with the
test files, the dead CircleCI config, and the RunTests script no package script
referenced. 221 packages leave the lockfile. @babel/polyfill stays: the main
webpack config and main.dev.js both import it.

The producer and proxy table rows passed the monospace font via a "styles"
prop, which React does not recognise, so the font never applied. Renaming it
to "style" clears the react/no-unknown-property errors and makes those account
names render monospaced as intended.

Index.childContextTypes declared a legacy context type that nothing provided:
there is no getChildContext anywhere, and the persistor is reached through
window.persistor instead. Removing the declaration also retires the last use of
the PropTypes import in that file.

yarn lint now exits 0. The 1878 warnings are unchanged.

Notarization is handled by the hooks: notarize.js notarizes each .app on
afterSign, and staple.js notarizes and staples the disk images on
afterAllArtifactBuild. The built-in path was never configured, so every macOS
build logged "skipped macOS notarization: `notarize` options were unable to be
generated" directly alongside the real signing output.

Setting it to false states that the hooks own notarization and stops a benign
message from reading like a signing failure.

Bumps [browserslist](https://github.com/browserslist/browserslist) from 4.17.0 to 4.29.0.
- [Release notes](https://github.com/browserslist/browserslist/releases)
- [Changelog](https://github.com/browserslist/browserslist/blob/main/CHANGELOG.md)
- [Commits](browserslist/browserslist@4.17.0...4.29.0)

---
updated-dependencies:
- dependency-name: browserslist
  dependency-version: 4.28.9
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>