feat(eslint): Enforce that ts-expect-error is used (#8987)

Enforce that `@ts-expect-error` is used instead of `@ts-ignore`. This is
done by updating the `typescript-eslint/ban-ts-comment` rule.

https://typescript-eslint.io/rules/ban-ts-comment/

Author: AbhiPrasad

packages/core/src/integrations/inboundfilters.ts

@@ -177,7 +177,7 @@ function _getPossibleEventMessages(event: Event): string[] {
 
   let lastException;
   try {
-    // @ts-ignore Try catching to save bundle size
+    // @ts-expect-error Try catching to save bundle size
     // eslint-disable-next-line @typescript-eslint/no-unsafe-member-access
     lastException = event.exception.values[event.exception.values.length - 1];
   } catch (e) {

packages/eslint-config-sdk/src/index.js

@@ -26,13 +26,9 @@ module.exports = {
         // Unused variables should be removed unless they are marked with and underscore (ex. _varName).
         '@typescript-eslint/no-unused-vars': ['error', { argsIgnorePattern: '^_' }],
 
-        // Make sure that all ts-ignore comments are given a description.
-        '@typescript-eslint/ban-ts-comment': [
-          'warn',
-          {
-            'ts-ignore': 'allow-with-description',
-          },
-        ],
+        // Do not use ts-ignore, use ts-expect-error instead.
+        // Also make sure that all ts-expect-error comments are given a description.
+        '@typescript-eslint/ban-ts-comment': 'error',
 
         // Types usage should be explicit as possible, so we prevent usage of inferrable types.
         // This is especially important because we have a public API, so usage needs to be as