Update e2e test to reflect change in Chrome

Previously Chrome would ignore an attempt to navigate to a restricted
URL like an extension page that is not web accessible. In a recent
Chrome update, this has changed. Now it does perform the navigation,
but to an error page that explains that the request was invalid.

The last assertion, responsible for checking that the warning page is
still shown, has been removed. The test still ensures the main wallet
UI is not loaded, that assertion was not needed.

test/e2e/tests/phishing-detection.spec.js

@@ -124,10 +124,6 @@ describe('Phishing Detection', function () {
 
         // Ensure we're not on the wallet home page
         await driver.assertElementNotPresent('[data-testid="wallet-balance"]');
-        // Ensure we're still on the warning page, meaning that the navigation failed
-        await driver.findElement({
-          text: 'continuing at your own risk',
-        });
       },
     );
   });