Switching Pilot account is not working well in Meta Mask

[jfschwarz]

When switching the connected address in Meta Mask this should be reflected in Pilot, but users report that they are unable to connect Pilot to the desired account. see this internal discord chat, for example: https://discord.com/channels/881881751369175040/1169364104373354586/1320714892482711562

Steps to reproduce:

• Make sure that https://connect.pilot.gnosisguild.org/ is connected to at least one MetaMask account
• Try to set up a route with another, still unconnected Meta Mask account as Pilot

Note:
If https://connect.pilot.gnosisguild.org/ isn't connected to any MM account, it will actually present a connection confirmation modal and you are able to connect the desired Pilot address.

[frontendphil]

Managing routes and connections through the extension might make this harder than it needs to be. @jfschwarz has an idea to extract the route configuration UI into the connect.pilot.gnosisguild.org domain. A small app that contains the current behavior. This would have the advantage that we wouldn't need to manage the MetaMask connection through an iframe, but it could be connected to the same host.

[frontendphil]

Postponing a fix in the current app version in favor of implementing #469 should also eliminate this bug. I'm keeping it open for visibility, though.

[frontendphil]

I tested this today, and it is fixed with the latest changes to the new routes config in the companion app.