fix: Check caveat in invokeKeyring

[FrederikBolding]

Inspect permission and check caveat in invokeKeyring.

---

Note

High Risk
Tightens authorization for keyring Snap invocation; incorrect caveat handling could block legitimate calls or leave overly broad access if misimplemented.

Overview
wallet_invokeKeyring now verifies the dapp is connected to the requested Snap, not just that it holds the broad wallet_snap permission.

The handler switches from PermissionController:hasPermission to getPermission, reads the SnapIds caveat, and only proceeds when the target snapId is listed for the origin. Otherwise it returns the existing “not connected” error. Tests and handler metadata were updated to mock getPermission with caveat data (or null when denied). Jest line coverage threshold was bumped slightly (99.22 → 99.23).

^{Reviewed by Cursor Bugbot for commit 87f29a9. Bugbot is set up for automated code reviews on this repo. Configure here.}

[Mrtenz]

Should be noted that this is technically a breaking change.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.60%. Comparing base (5ee78bd) to head (87f29a9).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #4128   +/-   ##
=======================================
  Coverage   98.60%   98.60%           
=======================================
  Files         429      429           
  Lines       12511    12513    +2     
  Branches     1978     1977    -1     
=======================================
+ Hits        12336    12338    +2     
  Misses        175      175           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.