feat: publish v6 with ESLint v10 migration completion

[MikeMcC399]

BREAKING CHANGE:

Republish of 5.4.0 with the following changes as new major version:

Remove deprecated eslint-plugin-cypress/flat configuration
Use eslint-plugin-cypress instead
Update globals to 17.3.0

Other changes:
Add package type commonjs
Documentation updates related to flat configuration
Update Node.js to 24.13.1

PR #298 had incomplete BREAKING message so it was published as 5.4.0 instead of 6.0.0

[cypress-app-bot]

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.

[jennifer-shehane]

Ahhh, it looked right when I checked it :/

[cypress-app-bot]

🎉 This PR is included in version 6.0.0 🎉

The release is available on:

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

Your semantic-release bot 📦🚀

[MikeMcC399]

@jennifer-shehane

Ahhh, it looked right when I checked it :/

I'm very sorry and it was a simple oversight on my part. Thanks for merging this one to get the right version out there.

You might like to deprecate the accidental 5.4.0 release on the npm registry https://www.npmjs.com/package/eslint-plugin-cypress/v/5.4.0 to hide it from view. Renovate etc. would then not try to use it.

[jennifer-shehane]

The breaking change commit message requirement is the worst honestly.

I've deprecated the 5.4.0 version in npm and marked the 5.4.0 GitHub release as deprecated

[MikeMcC399]

@jennifer-shehane

Thank you very much for tidying up after me and editing the release notes! That all looks good now.

For instance npm install eslint-plugin-cypress@5 will pick up only 5.3.0, not the deprecated 5.4.0.