[Bug]: Background - Terminate service worker and try to login to the wallet: `Cannot call write after a stream was destroyed`

Describe the bug

If you terminate service worker and then try to login to the wallet, without refreshing you get the: Cannot call write after a stream was destroyed error in the UI and cannot login.
You can work around the issue just by refreshing the browser, so it's not severe. However, reporting in case this needs to be investitgated further in the context of the infinite loading issues, or if there are Sentry issues which are just that.

This is error appears on the console when you terminate the service worker: Error#1: PortDuplexStream - disconnected

Expected behavior

No response

Screenshots/Recordings

https://github.com/user-attachments/assets/818b6b94-3d79-4932-8421-47e0a30b96ec

Steps to reproduce

1. Open MetaMask in full view and log in
2. Open a new tab and go to chrome://serviceworker-internals/?devtools
3. Look for the MM extension Id
4. Click Stop on the service worker for your extension
5. Go to MetaMask tab
6. Without refreshing, lock it
7. Try to unlock it
8. See error
   (same happens if you try to reveal the priv key )

Error messages or log output

Detection stage

In production (default)

Version

13.1.2

Build type

None

Browser

Chrome

Operating system

Linux

Hardware wallet

No response

Additional context

No response

Severity

No response

Start by reproducing the service-worker termination and wallet unlock steps in Chrome, then trace the PortDuplexStream - disconnected and Cannot call write after a stream was destroyed errors. Done means locking, unlocking, and revealing the private key work without refreshing after the service worker is stopped.