Confirmations redesign - add e2e for re-designed signature request message pages

[jpuri]

Create e2e tests to support the new confirmation/signature redesign

[seaona]

Test Scenarios

• [ ] Headers
  • [ ] Account details display address (can be copied) and balance with the correct currency
  • [ ] (See comment below) Selected account not the current one warning is displayed when a different account than the connected one is selected
• [ ] Signature domain section (per signature type)
  • [ ] Request from displays the url with HTTP warning if using HTTP instead of HTTPS
  • [ ] Interacting with displays the verifying contract address
• [ ] Signature message section (per signature type)
  • [ ] Primary type is correctly displayed
  • [ ] Message info matches the one we pass on the test dapp (no missing fields, correct identation etc)
• [ ] Navigation (signatures only)
  • [ ] I can navigate through multiple signatures
  • [ ] I can reject all signatures at once
  • [ ] I can reject/accept signatures one by one
• [ ] Navigation (mix transaction + signatures)
  • [ ] I can navigate through multiple signatures and transactions
  • [ ] I can reject all signatures and transactions at once
  • [ ] I can reject/accept signatures and transactions one by one
• [ ] Metrics
  • [ ] check we are tracking that it's the redesigned UI being used (while we have both new and old co-existing). For this we can add the value redesigned_confirmation to the ui_customizations property of all signature events when the redesigned UI is being displayed
  • [ ] check we are tracking opening of account info modal
• [ ] Malformed signatures

Manual Test Scenarios

• [ ] Specific styling topics
  • [ ] In dark mode, all the components keep following the style
  • [ ] In another language, all components keep following the style
• [ ] Hardware Wallets
  • [ ] I can sign typed v4 signatures with a hardware wallet
  • [ ] I see the info warnings for using hardware wallets
  • [ ] I see an error in the dapp when trying to sign non supported signatures (typed v2, typed)

[digiwand]

Hey team! Please add your planning poker estimate with Zenhub @cryptotavares @pedronfigueiredo

[seaona]

(Needs more input) Selected account not the current one warning is displayed when a different account than the connected one is selected

Adding explanation to this point, so it's clearer: it refers to the case when there is a miss-match between the account that's connected to the dapp and the currently selected account (not connected). We display the following warning in the current design and we should support something similar in the re-design:

[cryptotavares]

@seaona I see that behaviour on transactions but not on signatures 🧐

[bschorchit]

I think we used to have that for signatures, but we lost it when we updated the header for signatures. We can consider re-introducing it again once we have the alert system.