[Bug]: Transactions - Cannot destructure property 'chainId' of 'M' as it is undefined

### Describe the bug

Error captured by our e2e where the wallet breaks with this error:

`Cannot destructure property 'chainId' of 'M' as it is undefined`

### Expected behavior

_No response_

### Screenshots/Recordings

### Steps to reproduce

Captured by our e2e:
- https://github.com/MetaMask/metamask-extension/actions/runs/24119827127/job/70373795332
- https://github.com/MetaMask/metamask-extension/actions/runs/24102337818/job/70318271974

### Error messages or log output

```shell

```

### Where was this bug found?

Internal release testing

### Version

main

### Build type

None

### Browser

Chrome

### Operating system

Linux

### Hardware wallet

_No response_

### Additional context

_No response_

### Severity

_No response_

[Jira issue](https://consensyssoftware.atlassian.net/browse/MCTP-163)

### Expected behavior

No response

### Screenshots/Recordings

No response

### Steps to reproduce

Captured by our e2e:
- https://github.com/MetaMask/metamask-extension/actions/runs/24119827127/job/70373795332
- https://github.com/MetaMask/metamask-extension/actions/runs/24102337818/job/70318271974

### Error messages or log output

```shell

```

### Where was this bug found?

No response

### Version

main

### Build number

No response

### Build type

None

### Browser

Chrome

### Operating system

Linux

### Hardware wallet

No response

### Additional context

No response

### Severity

Sev2

Start by reviewing the linked e2e job runs to find the failing transaction flow and the surrounding error context. Trace the source of the undefined value behind the chainId destructuring failure, then verify the fix against the captured scenario and add a regression test if the relevant test location becomes clear.

Written by the indexing model from the issue text.