feat(core): Remove health check transaction filters

[Lms24]

This PR removes the ignoreTransactions default values which were all patterns trying to identify health check transactions.

We remove these because:

• We now have server-side inbound filters that are configurable in the Sentry UI
• Having two filters (SDK and Sentry backend) is more than unintuitive for users
• The patterns between the SDK and the Sentry backend filters were slightly different
• There's no other SDK that has client-side health check transaction filtering
• There simply is no safe way to filter such transactions without dropping false positives. This ofc also applies to the server-side filter but it's better to have this questionable heuristic only in one place than two.

Implementation note: Decided to remove the entire defaults array b/c there's no point in keeping around an empty array. Therefore, I also removed the ignoreTransactionDefaults option. We can re-add all of this if we ever want to filter out something by default again but for now, I'd argue the bundle size reduction is worth removing this code.

[github-actions]

size-limit report 📦

Path	Size
@sentry/browser (incl. Tracing, Replay, Feedback) - Webpack (gzipped)	77.24 KB (-0.04% 🔽)
@sentry/browser (incl. Tracing, Replay) - Webpack (gzipped)	68.51 KB (-0.05% 🔽)
@sentry/browser (incl. Tracing, Replay with Canvas) - Webpack (gzipped)	72.42 KB (-0.05% 🔽)
@sentry/browser (incl. Tracing, Replay) - Webpack with treeshaking flags (gzipped)	62.02 KB (-0.06% 🔽)
@sentry/browser (incl. Tracing) - Webpack (gzipped)	32.69 KB (-0.09% 🔽)
@sentry/browser (incl. browserTracingIntegration) - Webpack (gzipped)	32.69 KB (-0.09% 🔽)
@sentry/browser (incl. Feedback) - Webpack (gzipped)	30.86 KB (-0.16% 🔽)
@sentry/browser (incl. sendFeedback) - Webpack (gzipped)	30.86 KB (-0.16% 🔽)
@sentry/browser - Webpack (gzipped)	22.15 KB (-0.22% 🔽)
@sentry/browser (incl. Tracing, Replay, Feedback) - ES6 CDN Bundle (gzipped)	75.67 KB (-0.11% 🔽)
@sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (gzipped)	67.41 KB (-0.13% 🔽)
@sentry/browser (incl. Tracing) - ES6 CDN Bundle (gzipped)	33.2 KB (-0.26% 🔽)
@sentry/browser - ES6 CDN Bundle (gzipped)	24.69 KB (-0.16% 🔽)
@sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (minified & uncompressed)	210.92 KB (-0.17% 🔽)
@sentry/browser (incl. Tracing) - ES6 CDN Bundle (minified & uncompressed)	99.64 KB (-0.36% 🔽)
@sentry/browser - ES6 CDN Bundle (minified & uncompressed)	73.8 KB (+0.04% 🔺)
@sentry/browser (incl. Tracing) - ES5 CDN Bundle (gzipped)	36.26 KB (-0.28% 🔽)
@sentry/react (incl. Tracing, Replay) - Webpack (gzipped)	68.8 KB (-0.04% 🔽)
@sentry/react - Webpack (gzipped)	22.17 KB (-0.21% 🔽)
@sentry/nextjs Client (incl. Tracing, Replay) - Webpack (gzipped)	85.25 KB (+0.01% 🔺)
@sentry/nextjs Client - Webpack (gzipped)	49.62 KB (-0.09% 🔽)
@sentry-internal/feedback - Webpack (gzipped)	17.14 KB (0%)

[mydea]

Should we add a note here that they are dropped by default for projects created after X? As I guess that is the case here...? And add a note like "If your project was created before X, you can enable the inbound filter for this at Y"?

[Lms24]

I think the server side inbound filter was turned on for all projects 🤔 I checked for projects in Sentry that were created way before we introduced the filter and there it's also turned on.

[Lms24]

actually, I'm not too sure anymore

• seems like the filter was supposed to be disabled by default first (Inbound Filter for HealthChecks sentry#46731)
• later, we changed it to enabled for new projects (feat(inbound-filters): Turn on some filters for new Javascript projects sentry#62654)
  Will keep looking

[Lms24]

Ok, so even the projects in my private org have the filter turned on and I definitely didn't flip any switches there. I didn't find additional PRs that would have changed the defaults in older project but I asked in slack (#discuss-issues) to be sure.

[Lms24]

Talked to the issues team; the health check transaction filter is on by default for all (old and new) projects. So we should be good to go @mydea 👍