Follow up fixes for eslint 9 changes

[ricellis]

PR summary

A couple of fixes related to the eslint 9 changes in #2015 and recent dependabot update behaviour.

Fixes: part of i532

PR Checklist

Please make sure that your PR fulfills the following requirements:

• The commit message follows the
  Angular Commit Message Guidelines.
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• New tests
• Build/CI related changes
• Documentation content changes
• Other (please describe)

What is the current behavior?

#2015 included eslint-config-prettier in the package-lock.json but not the package.json (this was my error as I tried to cleanup the imports to just what we needed). It worked because npm ci kept the module around, but now dependabot is trying to clean it up as part of other updates e.g. #2019 and that causes failure.

Also there has been some drift on the eslint related dependabot groups due to changes and moves. This means we are missing some eslint related imports from the group and eslint plugins should be updated independently of eslint. The major version update is stopping plugins receiving updates in the group (we can manually ignore the major to split the group, but in general it seems better to have 2 groups). The patch level ignore is also going to delay a (harmless from this perspective) redos CVE resolution in the depoendency chain.

What is the new behavior?

• Add eslint-config-prettier to package.json and associated package-lock.json cleanup.
• Two dependabot groups eslint and eslint-plugins
• Remove patch level ignores for eslint* and @typescript-eslint/* (they run only weekly anyway)

Does this PR introduce a breaking change?

• Yes
• No

Other information