[Snyk] Security upgrade eslint from 7.32.0 to 9.26.0

[cc-prodsec]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• packages/internal-lib-build/package.json
• packages/internal-lib-build/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Uncontrolled Recursion SNYK-JS-ESLINT-15102420	623

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[cc-prodsec]

This major version upgrade from v7 to v9 introduces significant breaking changes, most notably the mandatory switch to a new "flat" configuration file format (<code>eslint.config.js</code>). The old <code>.eslintrc</code> format is deprecated and no longer supported by default in v9.

Highlights:

• Configuration File: You must migrate your existing <code>.eslintrc</code> file to the new <code>eslint.config.js</code> flat config format. ESLint provides a migration tool (<code>npx @eslint/migrate-config</code>) to assist with this process.
• Node.js Version: Support for Node.js versions below 18.18.0 has been dropped.
• Rule Changes: Several rules have been removed (e.g., <code>require-jsdoc</code>, <code>valid-jsdoc</code>), and the behavior of others has changed (e.g., <code>no-unused-vars</code> now checks <code>catch</code> block errors by default).

Source: ESLint documentation
Recommendation: Create a new branch, run the configuration migrator tool, and manually verify the new <code>eslint.config.js</code> file. Update any incompatible plugins and address new linting errors before merging.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

[cc-prodsec]

⛔ Snyk checks have failed. 1 issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (1)
⛔	Open Source Security	0	0	0	1	1 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.