[Bug]: Connect - Queuing connect requests from different dapps causes to display all domains as the first domain that made the request

[seaona]

Describe the bug

Queuing connect requests from different dapps causes to display all domains as the first domain that made the request.

Note that in current production 12.9.3, the requests are not queued, so the issue is not present there.

Expected behavior

Display the correct domain for each request

Screenshots/Recordings

connect-incorrect-domain.mp4

Steps to reproduce

1. Open one browser tab and go to a dapp ie https://metamask.github.io/test-dapp/
2. Open another browser tab and go to Uniswap https://app.uniswap.org/swap
3. Click Connect to the test dapp
4. Without accepting or rejecting, go to Uniswap
5. Click Connect to Uniswap
6. Navigate to both requests and see how both domains display the test-dapp one
7. Cancel the first request, the one coming from the test dapp
8. See how the second request still displays the incorrect domain (test dapp) instead of uniswap

Error messages or log output

Detection stage

During release testing

Version

12.10.0

Build type

None

Browser

Chrome

Operating system

Linux

Hardware wallet

No response

Additional context

No response

Severity

No response

[seaona]

Note: I added the sev1 label since this seems like a security issue, but feel free to re-assess if needed @adonesky1 🙏

[adonesky1]

I believe the issue is introduced by this commit, this PR, which makes some updates to the confirmation navigation system