feat: Add snap_trackError method for error tracking through Sentry

[Mrtenz]

This adds a new RPC method snap_trackError, which can be used to track errors in Sentry. It accepts a name, message, and stack, which should be turned into a proper Error class again on the client end before sending it to Sentry with Sentry.captureException.

To make the API a bit easier to use, I've added a getJsonError helper function which takes an error (string, Error class, or other value) and turns it into the properties expected by snap_trackError:

import { getJsonError } from '@metamask/snaps-sdk';

try {
  // ...
} catch (error) {
  await snap.request({
    method: 'snap_trackError',
    params: {
      error: getJsonError(error),
    },
  });
}

[Mrtenz]

@metamaskbot update-pr

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.23%. Comparing base (26b4c48) to head (49b4128).
Report is 6 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3498   +/-   ##
=======================================
  Coverage   98.22%   98.23%           
=======================================
  Files         405      406    +1     
  Lines       11412    11453   +41     
  Branches     1779     1778    -1     
=======================================
+ Hits        11210    11251   +41     
  Misses        202      202           

☔ View full report in Codecov by Sentry.
📢 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.

[FrederikBolding]

Do we actually need to check for full JSON validity here?

[Mrtenz]

It's what we did previously, I'm not sure if it's really needed, but kept it to be on the safe side.

[Mrtenz]

@metamaskbot update-pr