🐛 Use startsWith for the wc:// check in the UriService

[AlexV525]

Description

Use startsWith instead of contains to only escape wc:// deeplink from the service.

Resolves #329

[Copilot]

Pull request overview

Fixes overly broad WalletConnect deeplink detection in UriService by ensuring only URIs that start with wc:// are treated as the generic WalletConnect scheme (and therefore “not installed”), preventing false negatives for custom schemes like demowc://.

Changes:

• Replace contains('wc://') with startsWith('wc://') in UriService.isInstalled to avoid rejecting custom wallet schemes that include wc:// later in the string.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The comment says this only filters out a "generic wc://", but the new condition returns false for any URI that starts with wc:// (including wc://<something>). Update the comment to match the actual behavior (e.g., clarify that any WalletConnect wc:// scheme is treated as not-installed).

Suggested change

	// If the wallet is just a generic wc:// then it is not installed
	// Treat any WalletConnect wc:// scheme URI as not installed

[Copilot]

This changes installation-detection behavior; please add a unit test covering both cases: wc://... returns false, while custom schemes that merely contain wc:// later in the string (e.g. demowc://) are not incorrectly rejected. This will prevent regressions of issue #329.