tools: enable eslint concurrency mode

[JLHwung]

In this PR we enable the ESLint --concurrency mode. Per report from TIME(1), a cache-missed eslint job has improved from 75 seconds to 25 seconds on my machine. In the cache-hit scenario, both mode exit in less than 2 seconds.

[anonrig]

We also bumped all eslint deps. Linter is still happy, no code changes are required.

Can you open a different pull-request for this?

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.69%. Comparing base (7547e79) to head (7831d51).
⚠️ Report is 1256 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #62352 +/- ##
==========================================
- Coverage 91.60% 89.69% -1.91% 
==========================================
Files 337 676 +339 Lines 140745 206693 +65948 Branches 21802 39584 +17782 ==========================================
+ Hits 128925 185389 +56464 - Misses 11595 13442 +1847 - Partials 225 7862 +7637 

see 461 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[JLHwung]

We also bumped all eslint deps. Linter is still happy, no code changes are required.

Can you open a different pull-request for this?

Sure, open #62356.

[anonrig]

Can you update this PR?

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/71952/

[JLHwung]

It seems that CI errors are not related, could anyone restart the CI?

[github-actions]

This pull request has been marked as stale due to 90 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.

[JLHwung]

Not stale. I don't have the Jenkins CI permission so don't what is going on, could anyone restart the CI?