Extract route configuration into companion app

[frontendphil]

Currently, routes are configured inside the extension panel. This has some drawbacks:

• Routes will become more complex in the future, and the side panel does not offer the space needed to present them in a good way
• Connecting the wallet of a user through the extension is pretty complex and leads to bugs like Switching Pilot account is not working well in Meta Mask #422 that are hard/impossible to fix
• Present other issues, like not being able to connect to a dApp on every screen of the extension because of internal details (like a provider not being available at all times) (Confusing UX when trying to connect to an app before the initial route is configured #384)

Extracting the route configuration into a dedicated app can circumvent most of the issues mentioned above.

• The wallet could connect to the app directly (no indirection needed)
• We can use the whole browser window to render the configuration UI
• With a bit of work, we can create a version of the extension that works with dApps at all times and that requires only minimal integration with the route configuration UI

Todo

• bootstrap a new web-app (https://app.pilot.gnosisguild.org)
• create a shared components package so that UI elements can be re-used between apps
• use components also on landing page
• manage configs centrally
  • Typescript #555
  • eslint
  • tailwind
• make ser-kit ready to be used also in browsers (feat: replace assert with invariant in code to not require node environment ser-kit#30)
• add route management capabilities to the new app
• Label
  • Show
  • Edit
• Provider
  • show connected account
  • allow connect with MetaMask
  • allow connect with Walletconnect
  • Connection
    • Connect
    • Disconnect
• Chain
  • Show
  • Edit
• Avatar
  • add custom avatar
  • load available safes
  • edit avatar
• Role
  • Show selected role mod
  • Edit selected role
  • V1 role
    • Show
    • Configure
  • V2 role
    • Show
    • Configure
• New route
• Save edited route back to extension
  • Save routes
  • Warn about transactions before saving
• Dry run
• Migrate existing E2E tests to companion app
• remove route editing from the extension
  • tell the extension where to find the companion app
  • make sure the companion app is excluded from the content script injection
  • make it possible to remove routes from the list of all routes
  • open companion app to edit routes
  • remove old code
  • Keep list of routes (maybe as a popover/modal so that we can stay in the "active route" scenario)

Related issues

• Switching Pilot account is not working well in Meta Mask #422
• Cannot connect to Etherscan anymore #484
• Confusing UX when trying to connect to an app before the initial route is configured #384
• feat: replace assert with invariant in code to not require node environment ser-kit#30