Explore using sdk from webworker

This would improve in-browser performance in multiple ways:
1. Multiple pages can connect to single websocket connection via [shared worker](https://developer.mozilla.org/en-US/docs/Web/API/SharedWorker) (not compatible with mobile chrome)
2. All the RPC connection logic can run independently of browser window
3. We can cache whole sdk state in separate thread with all the computations and not block frontend
4. We will need to solve potentially running different environments (testnets) or connection to different chains at the same time

No files, tests, or entry points are identified. Begin by mapping the SDK's browser, RPC, websocket, and state-management architecture, then evaluate SharedWorker support and how simultaneous testnet or chain environments would be isolated. Done would require an agreed design and implementation plan for these cases.

Written by the indexing model from the issue text.