Enforce Angular template accessibility lint rules in core-web

Description

Re-enable the Angular template accessibility lint preset and fix the resulting violations. During the ESLint 9 migration ([#see Nx 23 + ESLint 9 issue]), @nx/eslint's flat angular-template preset began applying templateAccessibility (which the legacy eslintrc setup did not enforce). To keep that migration behavior-neutral, the accessibility rules were disabled via per-project overrides in the Angular eslint.config.mjs files. This issue turns them back on and fixes the code.

Rules to re-enable (@angular-eslint/template/*)

alt-text, click-events-have-key-events, elements-content, interactive-supports-focus, label-has-associated-control, mouse-events-have-key-events, no-autofocus, no-distracting-elements, role-has-required-aria, table-scope, valid-aria

Measured scope

~191 violations across ~95 template files. Concentration:

Dominant rules: elements-content (81), interactive-supports-focus (40), click-events-have-key-events (36), label-has-associated-control (27). The click/focus ones require real keyboard handlers (not auto-fixable).

Acceptance Criteria

• Remove the per-project templateAccessibility-disabling overrides from the Angular eslint.config.mjs files
• Fix all ~191 accessibility violations (add aria-label/content, keyboard handlers, for/id associations, remove autofocus, etc.)
• nx run-many -t lint --exclude=tag:skip:lint passes with the accessibility rules enabled
• No behavioral regressions in the affected components (manual smoke where keyboard handlers were added)

Additional Context

• Can be split per-area (e.g. dotcms-ui first, then libs) to keep PRs reviewable.
• Part of epic #32713.

Start with the Angular eslint.config.mjs files and remove the per-project templateAccessibility-disabling overrides. Work through the affected Angular templates, especially dotcms-ui and the dot-rules, edit-ema, edit-content, image-editor, ui, and portlet areas, then run nx run-many -t lint --exclude=tag:skip:lint. Done means all listed accessibility violations are fixed, lint passes, and keyboard-related changes have no behavioral regressions.