Add dApp connection flow with a basic design

[clauxx]

Feature Issue

User Story

As a user, I want to connect to dApps so that they can send me signing requests in the future.

Description

In order for the user to be able to receive signing requests (e.g. transactions), they should be able to connect to a dApp via a QR code. At this point we don't care about design fidelity, so we should aim for the simplest solution. As such, we should use the global QR code scanner for this flow and the connection from the account page will be handled separately.

Design link

Acceptance Criteria

• The user can scan wallet connect's connection requests from the global QR scanner (use the first account in the list)
• The wallet connect scanning should be hidden behind the feature flag
• After scanning, the user should see a screen that would show the dApp metadata (name, icon, url) and the decline/connect buttons
• When pressing connect, the dApp should be successfully connected
• When done, the user should be redirected back to the screen where the scanner was opened from
• When done, the success toast should appear
• If scanning or the connection failed, show a toast with a generic error message
• The reviewing developers should have a clear understanding of how to test this flow

Notes