Fix/android startup times remove web3

[infiniteflower]

This PR removes Web3 in favor of just using Ethers to read values off a contract.

	With Web3	No Web3	Perf improvement
App Start	4920ms	658ms	~86% decrease
Logcat	6929ms	~2500ms	~63% decrease

App start and Logcat are 2 related but different measurements. Logcat is more closely related to visually looking at the app and seeing when it starts up.

Related issues:

1. App Performance Start-Up: Swap Optimizations metamask-mobile#10611
2. chore: Improve startup times on Android through Swaps changes metamask-mobile#10787

Manual testing steps

Refer to MetaMask/metamask-mobile#10787 for steps on how to test

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@ethersproject/contracts@5.7.0	None	0	250 kB	ricmoo
npm/js-sha3@0.8.0	None	0	52.9 kB	emn178
npm/ws@7.4.6	network	0	113 kB	lpinca

🚮 Removed packages: npm/@adraffy/ens-normalize@1.10.1), npm/@types/ws@8.5.3), npm/abitype@0.7.1), npm/cross-fetch@4.0.0), npm/eventemitter3@5.0.1), npm/is-arguments@1.1.1), npm/is-generator-function@1.0.10), npm/isomorphic-ws@5.0.0), npm/js-sha3@0.5.7), npm/setimmediate@1.0.5), npm/util@0.12.5), npm/web3-core@4.3.2), npm/web3-errors@1.1.4), npm/web3-eth-abi@4.2.0), npm/web3-eth-accounts@4.1.1), npm/web3-eth-contract@4.3.0), npm/web3-eth-ens@4.2.0), npm/web3-eth-iban@4.0.7), npm/web3-eth-personal@4.0.8), npm/web3-eth@4.5.0), npm/web3-net@4.0.7), npm/web3-providers-http@4.1.0), npm/web3-providers-ipc@4.0.7), npm/web3-providers-ws@4.0.7), npm/web3-rpc-methods@1.2.0), npm/web3-types@1.5.0), npm/web3-utils@4.2.2), npm/web3-validator@2.0.5), npm/web3@4.7.0), npm/ws@8.16.0), npm/zod@3.22.4)

View full report↗︎

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/ws@7.4.6

View full report↗︎

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

[infiniteflower]

@SocketSecurity ignore npm/ws@7.4.6

[martahj]

LGTM! Was not able to test with Android device but tested for basic regressions on iOs as instructed