[LATTICE] Error is shown in MM if the user doesn't sign/reject the trx in Lattice in less than 1 min

## Describe the bug

### Expected result:
The user should be able to sign/reject the trx on Ledger even after 1 min has passed.

### Actual result:
After 1 min of waiting, error is thrown in MM "signal is aborted without reason". After 1 min, the swap/bridge fails in MM, no matter if the trx is approved or rejected in Lattice.

The acceptance criteria is the following:
- the timeout should match those of Ledger or Trezor
- the transaction should not be cancelled or aborted until that time is up or the user has rejected/sign the transaction.

**Environment:**

Device: MacBook Pro M4 ; macOS Tahoe 26.3.1
Chrome version: 146
MM prod 13.22.0

### Expected behavior

_No response_

### Screenshots/Recordings

https://github.com/user-attachments/assets/463f2e03-fd22-409e-a913-cf0337d8c2e7

### Steps to reproduce

- connect MM with Lattice
- start the swap/bridge scenario
- wait with the signing/rejecting of the trx on Lattice for 1 min
- notice the UI error "signal is aborted without reason"
- after that, sign the trx in Lattice
- in MM, notice that the swap already failed

### Error messages or log output

```shell

```

### Where was this bug found?

Live version (from official store)

### Version

13.22.0

### Build type

None

### Browser

Chrome

### Operating system

MacOS

### Hardware wallet

GridPlus Lattice1

### Additional context

_No response_

### Severity

sev3

Reproduce the swap or bridge flow with a GridPlus Lattice1 and wait over one minute before signing or rejecting. Trace the Lattice transaction timeout and compare it with the Ledger and Trezor timeout behavior; done means the transaction remains active until the matching timeout or the user's action, without the abort error.

Written by the indexing model from the issue text.