fix(passport): User able to disconnect the wallet and still sign in using the earlier triggered MetaMask notification

[WinsCodes]

Description

User is able to disconnect the wallet and still sign in using the earlier triggered MetaMask notification

Steps to Reproduce

1. Goto 'https://passport-next.rollup.id/authenticate'
2. Select the option 'Connect with Wallet'
3. Select 'MetaMask' in the Connect Wallet-pop up
4. Connect a wallet and once connected click the 'Continue with <wallet_address>' button
5. Once the 'MetaMask Notification' window is displayed, try disconnecting the wallet and click 'Sign' on the MetaMask notification window.

Expected Behavior

If user is allowed to disconnect the connected wallet then tries Signing in his wallet - he should be notified that his wallet is now disconnected (or the user should not be allowed to disconnect his wallet once he has initiated the Sign in flow)

Actual Behavior

With the MetaMask Notification window still open - user able to disconnect his wallet and even post that sign in and proceed.

[maurerbot]

You can't go directly to https://passport-next.rollup.id/authenticat directly. You have to go to /authorize endpoint with your client id, etc. Can you confirm this is an issue still?

When going through the flow first with /authorize I am unable to reproduce.