Fix: WC verification wording

[katspaugh]

What it solves

Adjust the warning as per Derek's request.

🙏for implementing Verify API - caveat
your language for “mismatch” is a bit strong and also wrong - we do not flag this scenario as “high risk”. Can you pls make the messaging a bit more clear?

[github-actions]

Branch preview

✅ Deploy successful!

https://fix_wc_warning--walletweb.review-wallet-web.5afe.dev

[github-actions]

ESLint Summary View Full Report

Annotations are provided inline on the Files Changed tab. You can also see all annotations that were generated on the annotations page.

Type	Occurrences	Fixable
Errors	0	0
Warnings	0	0
Ignored	0	N/A

• Result: ✅ success
• Annotations: 0 total

---

^{Report generated by eslint-plus-action}

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	75.04% (+0.02% 🔼)	10109/13472
🔴	Branches	49.54% (+0.02% 🔼)	2055/4148
🔴	Functions	57.46% (+0.04% 🔼)	1498/2607
🟡	Lines	76.61% (+0.02% 🔼)	9145/11937

Test suite run success

1105 tests passing in 155 suites.

Report generated by 🧪jest coverage report action from 74a578f

[liliya-soroka]

We tried to go with a more general message because we have only an invalid state from the wallet connect without the original problem.
The case "has a domain that does not match the sender of this request" might be one of the reasons for unverified apps. Would it not be confusing in case of other reasons for "unverified" by Wallet Connect?

[katspaugh]

@liliya-soroka they verify only domains, so that message is adequate. See https://docs.walletconnect.com/web3wallet/verify

[liliya-soroka]

Ok, agreed, verified