Use Case

As a mongodb node driver developer
I want to use the latest major version of eslint (v10)
So that compatible plugins and dependent packages can be updated, promoting maintainability

User Experience

• eslint checks should pass with the same rule parity following the v9 non-flat configuration file

Dependencies

• A dependent core plugin (mocha) cannot be updated to the next major version until this change follows through, as it has reliance on a flat configuration file (ref: https://github.com/mongodb/node-mongodb-native/pull/4812)

Risks/Unknowns

• A simple transition could cause a lack of parity with v9 rules to source code (e.g: an added rule in v10 which supplants a rule in v9, might require source code changes), this is acceptable for tests, but not for source (ie: no breaking change should need be introduced)
• Dissimilar linting between repo's
• Other plugin incompatibility discoveries (prettier, tsdoc, simple-import-sort, etc)

Acceptance Criteria

Implementation Requirements

• v10 of eslint requires a [flat configuration file|https://eslint.org/docs/latest/use/configure/migration-guide]]
• After this change, eslint should pass all checks via `npm run check:lint` and other repo linting scripts which rely on eslint should pass as well
• .eslintignore will be supplanted by ["ignores" in the new eslint config|https://eslint.org/docs/latest/use/configure/ignore]

Testing Requirements

• Compare verbose output of main eslint checks to new v10 eslint checks, ensure all files are covered
• Smoke test rule changes actually are actually emitting errors/warns

Documentation Requirements

• N/A

Follow Up Requirements

• https://jira.mongodb.org/browse/NODE-7616