Solution for multiple wallet connect instances

[tmctl]

Description:
This offers a solution in the cases where there are multiple browser tabs open.

In testing by @deligrim :

I have reproduced the problem both on the current version of hedera-wallet-connect and in the latest version of AppKit test applications.

I think the problem is in the wallet-connect kernel \ relay server. The relay server sends a result message to the only last connected sign client for a given topic id, while causing it to throw an exception because it can't find the original request record.

I provided a workaround to this bug in PR by force reconnecting the requesting dApp instance to relay if it was not the last connected instance (among browser tabs).

Related issue(s):

Fixes #387

Notes for reviewer:

Checklist

• Documented (Code comments, README, etc.)
• Tested (unit, integration, etc.)

[tmctl]

@teacoat does this seem like a viable solution for dApps for having multiple browser tabs open?

[franfernandez20]

That's a fantastic improvement! However, this doesn't allow the user to interact with multiple tabs, it only enables interaction with the most recent tab they connected to. I believe it remains essential to address the issue of using multiple tabs simultaneously.

[kantorcodes]

Hmmm, having to close all other tabs would be similar to the current experience, I am also worried about maintaining any code that touches the relay directly in this way and would suggest end to end tests to keep track of this in case the base functionality changes again

[teacoat]

I think we should leave to this to walletconnect to resolve

[tmctl]

closing this as I think this seems to be outside of the scope of what we want to focus on here - hedera integration vs. walletconnect enhancements