feat: update eslint to v8

[JPeer264]

This upgrades our internal eslint config to use v8. Theoretically this is considered a breaking change. Since this is an internal @sentry-internal/* package, we can release this in a non-breaking fashion

With v8 couple of changes came. Some of them are affecting us, which required file changes:

• simple-import-sort/import got couple of fixes
• "Unused eslint-disable directive": Unused "eslint-disable" comments are now detected and marked as error
• import/export got a false positive, which affects most of our index barrel files (I didn't want to disable it entirely, so I added a global disable in each affected barrel file)
  • tracked here: import/export false positive with star reexports import-js/eslint-plugin-import#703

Merge checks

• Rebased before merge to get the latest changes updated with the new version

[github-actions]

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	8,754	-	9,086	-4%
GET With Sentry	1,752	20%	1,761	-1%
GET With Sentry (error only)	6,196	71%	6,153	+1%
POST Baseline	1,187	-	1,210	-2%
POST With Sentry	569	48%	597	-5%
POST With Sentry (error only)	1,020	86%	1,075	-5%
MYSQL Baseline	3,279	-	3,326	-1%
MYSQL With Sentry	417	13%	493	-15%
MYSQL With Sentry (error only)	2,671	81%	2,708	-1%

View base workflow run

[Lms24]

Theoretically this is considered a breaking change. Since this is an internal @sentry-internal/* package, we can release this in a non-breaking fashion

Before we merge this, let's check in with Electron, Lynx and React-Native SDK maintainers. They all use a 10.x version of @sentry-internal/eslint-config-sdk so we should make sure this change doesn't cause problems for them:

https://github.com/search?type=code&q=%40sentry-internal%2Feslint-config-sdk+owner%3Agetsentry+

I agree btw that we shouldn't have to stick to semver for this internal package. Let's just make sure we break no-one unexpectedly 😅

[JPeer264]

@Lms24 I just asked internally and it seems to be ok for the others