fix: filter SES from Sentry stack trace frames

[leotm]

Description

SES is shown at the top of the stack trace, but we don't have a lockdown (repairIntrinsics) option to hide it yet

this simply removes the SES frame from the Sentry error event stack trace

we identify this with ease by the filename, rather than the verbose context_line

here's an example of a SES Sentry error event stack trace frame that we remove:

    {
      "colno":25,
      "context_line":"        error=  construct(FERAL_ERROR, rest, new.target);",
      "filename":"app:///ses.cjs",
      "function":"Error",
      "in_app":true,
      "lineno":7575,
      "platform":"javascript",
      "post_context":[
        "Array"
      ],
      "pre_context":[
        "Array"
      ]
    },

https://docs.sentry.io/platforms/javascript/configuration/filtering

https://github.com/endojs/endo/blob/master/packages/ses/docs/reference.md#options-quick-reference

Related issues

Fixes: #8586

Manual testing steps

• create personal Sentry account
• npx @sentry/wizard
• update sentry.properties
• update app/util/sentry/utils.js
  • Sentry.init({dsn: xxx})
• yarn setup
• enable SES in debug-mode (here)

• <Button title='Try!' onPress={ () => { Sentry.captureException(new Error('First error')) }}/>
• test a handled Sentry.captureException('test')
• test a Sentry.nativeCrash()
• test an unhandled throw new Error('test')

• observe error on sentry.io
• Error(ses) no longer seen
• app:///ses.cjs frame no longer present in stack trace
• app:///ses.cjs still present in breadcrumbs

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Coding Standards.
• I've clearly explained what problem this PR is solving and how it is solved.
• I've linked related issues
• I've included manual testing steps
• I've included screenshots/recordings if applicable
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.
• I’ve properly set the pull request status:
  • In case it's not yet "ready for review", I've set it to "draft".
  • In case it's "ready for review", I've changed it from "draft" to "non-draft".

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[sonarcloud]

Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[github-actions]

E2E test started on Bitrise: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/70f511ec-47ef-4c78-b34d-7f23ce02d229
You can also kick off another Bitrise E2E smoke test by removing and re-applying the (Run Smoke E2E) label

[Cal-L]

Lgtm