fix-linting

Group the lint output by ESLint rule name instead of fixing errors in file order. Each rule cluster usually traces back to one root cause, so a single targeted fix can clear 4 to 10 errors at once. Re-run lint after each fix to keep the count accurate.

An "error typed value" message means a TypeScript type error is cascading, usually from a broken or unresolved import, so investigate the import chain. An "any typed value" message means loose typing from an `as any` cast or untyped spy, fixed at the typing source.

Broken imports from deleted or renamed modules resolve to an error type that cascades into surrounding code. Remove the dead import along with every usage, such as TestBed providers or stubs, rather than adding type casts.

First determine whether the team deliberately kept the deprecated API. If unintentional, migrate to the recommended replacement. If deliberate, suppress with an eslint-disable-next-line comment at each usage site, since the rule fires at usages, not import lines.

An `as any` cast introduces new no-unsafe-* violations because the value becomes untyped. Use `as unknown as T` with a scoped type alias instead, which satisfies the compiler without triggering unsafe-type rules.

Skip the clustering technique when there is only a single error in a single file; just fix it directly. The grouping and root-cause analysis overhead only pays off when errors span multiple rules and files.