chore: update jest and eslint to latest versions

[mareknovotny]

• Update jest from 30.0.0 to 30.4.2
• Update eslint from 8.30.0 to 10.0.0 (major version upgrade)
• Update @typescript-eslint/eslint-plugin from 5.47.0 to 8.66.0
• Update @typescript-eslint/parser from 5.47.0 to 8.66.0
• Update @types/jest from 29.2.4 to 30.0.0
• Update ts-jest from 29.4.5 to 29.4.12
• Add @eslint/js 10.0.0 as new dependency

Migration to ESLint v10 flat config format:

• Migrate from .eslintrc to eslint.config.cjs (new flat config format)
• Remove deprecated .eslintrc and .eslintignore files
• Configure Node.js and Jest globals in the new config

All tests pass (229 tests passing) and linter works correctly.

Thank you for submitting this pull request

fixes (please add the issue ID if it exists)

Description

How Has This Been Tested?

Checklist

• Tests added if applicable.
• Documentation updated if applicable.

Merge criteria:

• The commits and have meaningful messages; the author will squash them after approval or will ask to merge with squash.
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has manually tested the changes and verified that the changes work

Note: dist/cli/index.js and dist/gha/index.js are automatically generated by git hooks and gh workflows.

First time here?

This project follows git conventional commits pattern, therefore the commits should have the following format:

<type>(<optional scope>): <subject>
empty separator line
<optional body>
empty separator line
<optional footer>

Where the type must be one of [build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test]

NOTE: if you are still in a work in progress branch and you want to push your changes remotely, consider adding --no-verify for both commit and push, e.g., git push origin <feat-branch> --no-verify - this could become useful to push changes where there are still tests failures. Once the pull request is ready, please amend the commit and force-push it to keep following the adopted git commit standard.

How to prepare for a new release?

There is no need to manually update package.json version and CHANGELOG.md information. This process has been automated in Prepare Release Github workflow.

Therefore whenever enough changes are merged into the main branch, one of the maintainers will trigger this workflow that will automatically update version and changelog based on the commits on the git tree.

More details can be found in package release section of the README.

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟢	Statements	90.48% (-0.01% 🔻)	608/672
🟢	Branches	86.43%	293/339
🟢	Functions	88.96%	145/163
🟢	Lines	90.29% (-0.01% 🔻)	586/649

Show files with reduced coverage 🔻

St.❔	File	Statements	Branches	Functions	Lines
🟢	... / pr-configs-parser.ts	98.72% (-0.02% 🔻)	97.3%	100%	98.65% (-0.02% 🔻)

Test suite run success

229 tests passing in 19 suites.

Report generated by 🧪jest coverage report action from 0ab77bb

[mareknovotny]

also should fix GHSA-5p4m-2wfm-xmqj

[lampajr]

Thanks @mareknovotny, LGTM!

We should just revert the package.json version to 4.10.0 as this will be managed and increased as part of the release process (not ideal I agree)