feat!: Bump all packages and fix linting

[scagood]

Larger Changes

1. Drop support for node less than ^18.18.0 (this is inline with eslint package.json:180)
2. Drop support for eslint less than ^7.0.0

Smaller Changes

1. Migrate all message to messageId (for the update to eslint-plugin-eslint-plugin)
2. Bumped all packages (except eslint) to the latest version.
3. Replaced eslint-plugin-node with eslint-plugin-n
4. Replaced npm-run-all with npm-run-all2

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (bbcfcbf) to head (4db7f5d).
Report is 8 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #471   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           25        24    -1     
  Lines          649       653    +4     
  Branches       250       246    -4     
=========================================
+ Hits           649       653    +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[scagood]

From now, ESLint 9 is blocked by:

• eslint-doc-generator (https://github.com/bmish/eslint-doc-generator/blob/main/package.json#L48)
• @typescript-eslint/utils (https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/utils/package.json#L76)
• @typescript-eslint/parser (https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/parser/package.json#L52)

I could ignore those, as they're all dev deps 🤔

[aladdin-add]

this is a breaking change.

[scagood]

this is a breaking change.

The commits here are meant to be rebase merged, but its good that the title is representative of that too 😄

[aladdin-add]

what do you think splitting the PR to several smaller ones, for clearer changelogs?

[scagood]

The only one I would split out would be 9dcfd39 (#471)

However if that is the only way to convert the commits to changelog entries, I will split them into 4.

[aladdin-add]

I suggest splitting 4db7f5d and fc861bf to one - they introduced breaking changes.

[brettz9]

@scagood : if you want to resolve the conflicts and split out the changes, I'd be happy to do a review. Also, can team members do merges if for another's PR, or is the merging reserved for team leaders?