chore(deps): update @typescript-eslint/* dependencies to v6.0.0

[xaviermawet]

Description

Updated typescript-eslint to version 6.0.0 and resolved breaking changes using the official migration guide.

Additional context

Nothing.

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines and follow the PR Title Convention.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[bluwy]

Looks great! Thanks for making the changes without changing the source code, that makes it easier to review.

[ArnaudBarre]

Thanks for the update. This config was already a mess, but I'm ok with these changes at the root. I will maybe update some rules later on.
For the React template, we decided to update the configuration and go back to a minimal stater. I will update the version in #13749 with other changes

[xaviermawet]

Hi @bluwy, @ArnaudBarre,

Yes, the purpose of this PR was to upgrade to new configuration names and have the exact same ESLint configuration as before, without updating the code.

I had two options:

1. not extend stylistic and manually add the rules that were in recommended v5 but no longer in recommended v6
2. extend stylistic and disable the additional rules of stylistic v6 which were not in recommended v5 and conflicted with the current code.

I logically opted for the second solution which went in the direction of an additional quality of code.
The idea being to gradually remove these new deactivated rules (therefore activate them) in dedicated PRs.

@ArnaudBarre, do you want me to remove the changes from the React template to prevent conflicts with
#13749 where @typescript-eslint/* dependencies will be upgraded ?

Regards,

[ArnaudBarre]

Yeah I agree this is the best choice for this PR and going in the good direction.

Yeah I would prefer not having a state where the main branch has again another set of rules in case we push a fix of create-vite before I merge #13749

[xaviermawet]

I've just rebased my PR branch on top of main and reverted the commit that updated the React template to avoid conflicts with #13749.

Regards,

[ArnaudBarre]

Thanks for the update, LGTM