Currently the extension has explicit ts
import files (example - import * 'test.ts').
This is not a good pattern for node, as the
ts build will output js files. And thus during
the runtime the node process breaks as it cannot
find the imported file. On the Extension it does not
have any issues because of the bundling that we have
in place. It creates a reference to the path and as so
it can have ts and js files beig explicitly imported,
but in reality it is only running js.
The fix that we are doing here, is just to
remove the .ts file extension from any import (as the
ts file itself is already transpiled into js and
has the js file extension)

This is in line with the node version
that electron 23 is using

The NFTController is always fetching the
NFT image, even if the image is a data base64
encoded. Fetching anything other than http/https
is supported in the browser but not by node-fetch
(which uses the underlying http/https node native modules).
To fix this we will use the native node fetch
(available by default since node 18) to perform
any fetch actions that are not http/https.

There's an issue with node 18
where dns will resolve using ipv6
and not fallback to ipv4. This was
causing the tests to fail, because
localhost resolves to ::1:<port>
instead of 127.0.0.1:<port>. This
was preventing from running the tests
locally

When running the extension e2e tests
it is expected that the infura project
id is set to 00000000000000000000000000000000.
If not we might not be hitting the mockserver

Firefox generates a different runtime id
for the extension. In order to get the
actual runtime id, we can parse the url
from an internal connection created by either
the popup, notification or fullscreen extension

This method is not async in the browser.
Due to that on the Extension we are calling
it synchronously to go back to the home page
(from the phishing blocked script). When on Desktop
we proxy this requests to the actual browser, meaning
that the request will be async. This was causing
the phishing detection to not return to the extension
home page when clicking on the back to safety button.
Also, it is worth mentioning that the
protocol for chrome and firefox extensions are different.
So added a method to update the browser info
accordingly and route to the correct url.

snaps 0.32.2 updated the bundled from
webpack to browserify, so we need to reintroduce
this patch (now adpated to browserify)

trezor connect and isomorphic fetch were
overriding global.fetch. Open a topic
with lavamoat team to clarify why
setting the policy to write
would not identify that the global.fetch
was previously set.

Mock connectRemote env type constants

This test is skiped in the extension.
There is a bung in the snaps controller.