Replace dependency babel-eslint with @babel/eslint-parser ^7.11.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
babel-eslint → @babel/eslint-parser	dependencies	replacement	^10.1.0 → ^7.11.0

⚠️ Renovate's replacement functionality does not currently wire in the release age for a package, so the Minimum Release Age checks can apply. You will need to manually validate the Minimum Release Age for these package(s).

This is a special PR that replaces babel-eslint with the community suggested minimal stable replacement version.

---

Configuration

📅 Schedule: (in timezone US/Eastern)

• Branch creation
  • "every weekend"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: yarn.lock

/opt/containerbase/tools/corepack/0.34.6/14.18.2/node_modules/corepack/dist/yarn.js:2
process.env.COREPACK_ENABLE_DOWNLOAD_PROMPT??='1'
                                           ^^^

SyntaxError: Unexpected token '??='
    at wrapSafe (internal/modules/cjs/loader.js:1001:16)
    at Module._compile (internal/modules/cjs/loader.js:1049:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
    at Module.load (internal/modules/cjs/loader.js:950:32)
    at Function.Module._load (internal/modules/cjs/loader.js:790:12)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:76:12)
    at internal/main/run_main_module.js:17:47

[sentry]

Bug: Replacing babel-eslint with @babel/eslint-parser will cause the linting step to fail because a Babel config file is required by default but is not present.
_{Severity: HIGH}

Suggested Fix

Add parserOptions: { requireConfigFile: false } to the .eslintrc file. This will instruct @babel/eslint-parser not to look for a Babel configuration file, resolving the linting failure.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: package.json#L20

Potential issue: The project updates the ESLint parser from `babel-eslint` to
`@babel/eslint-parser`. The new parser, `@babel/eslint-parser`, defaults its
`requireConfigFile` option to `true`, meaning it requires a Babel configuration file
(like `.babelrc`) to be present. Since this project lacks such a file and does not
override this setting in its `.eslintrc` `parserOptions`, the `npm run lint` command
will fail. This will cause the CI build to fail, preventing the PR from being merged or
deployed.

_{Did we get this right? 👍 / 👎 to inform future reviews.}

[sentry]

Bug: The new @babel/eslint-parser requires Babel 7, but the project's configuration and dependencies are still on Babel 6, which will cause the linting process to fail.
_{Severity: CRITICAL}

Suggested Fix

To resolve the incompatibility, either upgrade the entire Babel ecosystem (core, plugins, presets) to version 7 to match the new parser, or revert to using babel-eslint which is compatible with the existing Babel 6 setup. A full upgrade would involve adding @babel/core and replacing babel-* packages with their @babel/* equivalents.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: package.json#L20

Potential issue: The project's dependencies and configuration are based on Babel 6,
including `babel-core` and various plugins/presets. This pull request introduces
`@babel/eslint-parser`, a package that requires Babel 7 (`@babel/core@>=7.2.0`). This
creates a major version incompatibility. When the `lint` script runs, ESLint will use
the new parser, which will fail because it cannot work with the existing Babel 6
ecosystem. This will cause the linting process to fail, breaking any build or CI
pipeline that includes it.

[sentry]

Bug: The project uses Babel 6, but the newly added @babel/eslint-parser requires Babel 7, which will cause ESLint parsing to fail.
_{Severity: MEDIUM}

Suggested Fix

To resolve the incompatibility, either upgrade the entire project to Babel 7 (including babel-core and related plugins) or find a version of the ESLint parser that is compatible with the existing Babel 6 setup.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: package.json#L20

Potential issue: The project's dependencies include `babel-core: ^6.24.1`, indicating it
is configured for Babel 6. The pull request introduces `@babel/eslint-parser: ^7.11.0`,
which is designed to work with Babel 7. This version mismatch will cause ESLint parsing
to fail when it encounters Babel-specific syntax, as the parser will not be compatible
with the project's existing Babel 6 configuration and plugins. This will break the
linting process during development and in CI pipelines.

[sentry]

Bug: The update to ESLint dependencies will break the linting process because eslint-config-mitodl still requires the removed babel-eslint, and the new @babel/eslint-parser is missing its @babel/core peer dependency.
_{Severity: HIGH}

Suggested Fix

To fix the linting failure, add @babel/core as a dev dependency to satisfy the peer dependency requirement of @babel/eslint-parser. Then, override the parser in the local .eslintrc configuration file by setting "parser": "@babel/eslint-parser" to ensure it is used instead of the one specified by eslint-config-mitodl.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: package.json#L20

Potential issue: The changes in `package.json` will break the ESLint setup. The removal
of the `babel-eslint` package will cause an error because a dependency,
`eslint-config-mitodl`, still requires it. This will lead to a "Cannot find module
'babel-eslint'" error when running the linter. Additionally, the newly added
`@babel/eslint-parser` requires `@babel/core` (version 7) as a peer dependency, which is
not present in the project's dependencies. The project currently uses the older
`babel-core` (version 6). These issues will cause the linting process to fail, blocking
CI/CD pipelines.