We renamed the eslint configuration to follow the recommended standards
so developers IDEs will pick up the configuration more easily.

The ruleset was adapted to follow a wider range of recommendations.
- eslint:recommended
- @typescript-eslint/recommended
- lit/recommended
- wc/recommended

In addition we now also force more kinds of spacing rules to avoid
IDEs having different opinions on how to format for example includes.

The only recommendation we don't want to follow is
- @typescript-eslint/no-inferrable-types.
We don't want to disallow being explicit.

Instead of turning off rules we cannot fully fulfill as of now, we are
now changing the configuration to warning. This will help developers
spotting mistakes more easy when writing code.

Rules that are currently in "warn" mode:
- @typescript-eslint/ban-types
- @typescript-eslint/no-explicit-any
- @typescript-eslint/no-this-alias

To only check for errors run in the Build directory:
- npx eslint ./Sources/TypeScript/ --quiet

We are removing the custom member ordering and preferring the default.
@typescript-eslint/member-ordering

Resolves: #100126
Releases: main
Change-Id: I6f09f82c0bdcde1aa3edec66b3b6ab028d5bb242
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/78040


Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Benni Mack <benni@typo3.org>
Reviewed-by: Oliver Hader <oliver.hader@typo3.org>
Tested-by: Benni Mack <benni@typo3.org>
Tested-by: Oliver Hader <oliver.hader@typo3.org>