AlphaWallet
Refactor WalletConnect OKHttp client usage
Refactor WalletConnectActivity, WCClient and WalletConnectService to remove the OKHttp client from WCClient and move ownership of all WC comms into WalletConnectService.
Currently, because the OKHttp client is created in WalletConnectActivity, and kept within each WCClient object, and each OKHttp client connect contains a link to the WalletConnectActivity context, the context is leaked when WalletConnectActivity is destroyed.
The OKHttp client should be constructed in WaletConnectService, using the service context.
@JamesSmartCell , I'm a bit confused here. OkHttpClient doesn't need context to start so how can it leak activity. Can you please guide me if I understood it wrong?
