Right now we're filtering out third-party extensions by looking for
stack traces that don't touch 'app:///_next'. However, third-party stack
traces do include the Sentry code that sends the error, and that
originates in 'app:///_next'. We need to filter out any events that do
not have 'app:///_next' events beyond that one Sentry frame.
Should've double-checked this before applying the filter =_=""" but
apparently filtering out `app:///` also filters out legitimate events,
since those files are prefixed by `app:///` as well.
Instead let's keep only `app:///_next` since that should include all our
static JS assets.
* chore(docs): turn off sentry sends for local dev
No point wasting quota on local dev, it's easy enough to disable the if
statements if you need to debug something with Sentry.
* ci: Autofix updates from GitHub workflow
Charis