feat: update eslint-plugin-eslint-plugin + update configs

[MichaelDeBoey]

Re-submission of mysticatea#41

---

BREAKING CHANGE: +eslint-plugin config now has extra rules from eslint-plugin-eslint-plugin

[codecov-commenter]

Codecov Report

Base: 97.17% // Head: 97.17% // Decreases project coverage by -0.00% ⚠️

Coverage data is based on head (5a94cbf) compared to base (0f90860).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files

@@            Coverage Diff             @@
##            alpha      #23      +/-   ##
==========================================
- Coverage   97.17%   97.17%   -0.01%     
==========================================
  Files          39       39              
  Lines         390      389       -1     
==========================================
- Hits          379      378       -1     
  Misses         11       11              

Impacted Files	Coverage Δ
lib/configs/+eslint-plugin.js	100.00% <ø> (ø)
lib/rules/arrow-parens.js	100.00% <ø> (ø)
lib/rules/block-scoped-var.js	98.64% <ø> (ø)
lib/rules/no-instanceof-array.js	93.33% <ø> (ø)
lib/rules/no-instanceof-wrapper.js	100.00% <ø> (ø)
lib/rules/no-literal-call.js	100.00% <ø> (ø)
lib/rules/no-this-in-static.js	100.00% <ø> (ø)
lib/rules/no-use-ignored-vars.js	100.00% <ø> (ø)
lib/rules/no-useless-rest-spread.js	94.87% <ø> (ø)
lib/rules/prefer-for-of.js	99.20% <100.00%> (-0.01%)	⬇️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[MichaelDeBoey]

@eslint-community/eslint-tsc @eslint-community/core-team @eslint-community/mysticatea-eslint-plugin Since this plugin is adhering the same semantic versioning policy as ESLint, adding new rules to a plugin would be a breaking change, so this PR would need to be released in a major release I guess?

[mdjermanovic]

adding new rules to a plugin would be a breaking change

I assume you mean adding new rules to configs exported from the plugin. I agree that should be a breaking change.

[MichaelDeBoey]

I assume you mean adding new rules to configs exported from the plugin

@mdjermanovic That's indeed what I meant 👍

@eslint-community/mysticatea-eslint-plugin I decided to make all the current outstanding PRs a breaking change & merge them into an alpha branch, so we can have 1 major release instead of one for every merged PR

[ota-meshi]

LGTM! Thank you!

[github-actions]

🎉 This PR is included in version 15.0.0-alpha.4 🎉

The release is available on:

• npm package (@alpha dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 15.0.0-beta.1 🎉

The release is available on:

• npm package (@beta dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 15.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀