feat: add ESLint rule to enforce named ILogger conventions

[ankitsharma101]

What it does

Resolves #17468.

This PR introduces a new custom ESLint rule (named-logger-check.js) to the private-eslint-plugin to enforce the new logger coding guidelines. Specifically, the rule ensures that:

1. console.* statements are not used inside @injectable() classes.
2. Injected ILogger instances are accompanied by an @named(...) decorator.
3. The string passed to @named follows the required naming convention: [optional-purpose]package-name:class-name#optional-suffix.
4. Files residing in electron-main are explicitly excluded from this check, as the DI container is not fully available during early bootstrap.

How to test

1. Automated Tests: Run the Mocha test suite in dev-packages/private-eslint-plugin to verify the AST logic and regex patterns.
2. Manual Verification: Add a temporary console.log("test") inside any @injectable class in the frontend (e.g., packages/core/src/browser/application-shell.ts). Run yarn lint packages/core and observe the custom ESLint error Use injected ILogger instead of console statements in @injectable classes.

Follow-ups

Aligning the rest of the codebase to pass this new rule. (Note: Existing violations are currently being addressed in PR #17541).

Breaking changes

• This PR introduces breaking changes and requires careful review. If yes, the breaking changes section in the changelog has been updated.

Attribution

Review checklist

• As an author, I have thoroughly tested my changes and carefully followed the review guidelines
• User-facing text is internationalized using the nls service (for details, please see the Internationalization/Localization section in the Coding Guidelines)

Reminder for reviewers

• As a reviewer, I agree to behave in accordance with the review guidelines

[sdirix]

Looks pretty good already! However we can only activate this if the rest of the codebase is migrated in a separate PR or within this PR as otherwise we have a lot of lint errors.

[sdirix]

Registering the rule here only exposes it under @theia/named-logger-check, it doesn't activate it. The rule isn't added to configs/errors.eslintrc.json (or any other config), so npm run lint never runs it and the "How to test" steps in the PR description won't produce an error.

[sdirix]

Missing the EPL license header and // @ts-check. Every other rule file has both, e.g. annotation-check.js. annotation-check.js also uses proper @typedef imports instead of the inline /** @type {any} */ casts here, worth following the same pattern.

[sdirix]

Missing the EPL license header here too.

[sdirix]

New rule isn't documented in the plugin README, which lists every other rule. Please add a named-logger-check entry.

[ankitsharma101]

Hi Stefan, thanks for the review! I've updated the rule with the requested license headers, added // @ts-check with proper JSDoc typedefs to satisfy type checking, and added documentation to the README. The rule remains disabled in errors.eslintrc.json as discussed to avoid build breaks during the migration. Ready for another look!