* Cypress: move verification tests to their own file
* Remove redundant cypress test
This does nothing that the verification test doesn't do better.
* Factor `beginKeyVerification` call out of `doTwoWaySasVerification`
... for more flexibility. This allows us to have tests where the other side
picks the verification method.
* Cypress test for incoming verification requests
* Update references to `VerificationRequestEvent`
* Update references to `Phase`
* update references to legacy `PHASE_*` constants
* Replace `request.canAccept` with `canAcceptVerificationRequest`
* Replace `VerificationRequest` with the interface throughout
* Minor strict type fixes
* Add a couple of tests
* Add WIP Sas cross-signing test
* Login after bot creation
* Figuring out how to make it work in ci
* Wait for `r0/login` to be called before bot creation
* Make waitForVerificationRequest automatically accept requests
... thereby making the `acceptVerificationRequest` helper redundant
* Clean up `deviceIsCrossSigned`
* combine `handleVerificationRequest` and `verifyEmojiSas`
* get rid of a layer
... it adds no value
* fix bad merge
* minor cleanups to new test
* Move `logIntoElement` to utils module
* use `logIntoElement` function
* Avoid intercept
* Avoid `CryptoTestContext`
---------
Co-authored-by: Richard van der Hoff <richard@matrix.org>
* Cypress: skip tests known to fail when using Rust crypto
... which means we can then run the cypress test suite against Element Web R to
check we aren't introducing regressions.
* Update cypress/e2e/register/register.spec.ts
* Use env var to detect rust crypto
* Hoist `skipIfRustCrypto` call earlier
