chore(ui): migrate ESLint to flat eslint.config.ts with typescript-eslint and import-x

[pfe-nazaries]

Context

The legacy ui/eslint.config.mjs was an early flat-config port: it still glued together hand-imported plugins (@typescript-eslint/eslint-plugin, @typescript-eslint/parser, eslint-plugin-prettier, eslint-plugin-simple-import-sort, eslint-plugin-unused-imports) and didn't use type-aware linting. This PR consolidates that config onto the canonical flat-config primitives and prepares the workspace for type-aware rules without changing any product behavior.

Description

• Renames ui/eslint.config.mjs → ui/eslint.config.ts and wires it through tseslint.config(...) so we can use the typescript-eslint meta-package and TS types in the config itself.
• Replaces the separate @typescript-eslint/eslint-plugin + @typescript-eslint/parser entries with typescript-eslint. Enables parserOptions.projectService with tsconfigRootDir: import.meta.dirname so the parser uses the canonical TS project graph. events-timeline.test.tsx is opted into allowDefaultProject because TypeScript skips it in favor of its .ts sibling.
• Replaces eslint-plugin-prettier (which runs Prettier through ESLint) with eslint-config-prettier/flat (which only disables conflicting rules).
• Consolidates eslint-plugin-simple-import-sort + eslint-plugin-unused-imports into eslint-plugin-import-x using its recommended + typescript flat configs. Wires the resolver chain via createTypeScriptImportResolver + createNodeResolver and adds jiti so ESLint can load the .ts config.
• Adds eslint.config.ts to tsconfig.json exclude and to the ESLint own ignore list to keep it out of the typecheck/lint passes.
• Applies eslint --fix for the new import-x/order rule across the workspace (alphabetised, blank lines between groups). All churn is purely import grouping/consolidation — no runtime code changes.
• Adds a ui/CHANGELOG.md entry under [1.28.0] / 🔄 Changed.

The migration is intentionally behavior-preserving: import-x/export is kept off so pre-existing duplicate exports stay tracked separately, and lint:check stays under the existing --max-warnings 40 budget.

Steps to review

1. pnpm install (regenerates the lockfile entries for the new plugins).
2. pnpm run lint:check should pass under --max-warnings 40.
3. pnpm run typecheck should pass.
4. Skim ui/eslint.config.ts and compare with the previous .mjs to confirm there are no rule changes other than the documented ones.
5. Spot-check a couple of the touched files (e.g. ui/components/findings/table/resource-detail-drawer/resource-detail-drawer-content.tsx, ui/components/ui/sidebar/sidebar.tsx) — the only edits are import consolidation and blank lines between import groups.

Checklist

Community Checklist

• This feature/issue is listed in here or roadmap.prowler.com
• Is it assigned to me, if not, request it via the issue/feature in here or Prowler Community Slack

• Review if the code is being covered by tests.
• Review if code is being documented following this specification https://github.com/google/styleguide/blob/gh-pages/pyguide.md#38-comments-and-docstrings
• Review if backport is needed.
• Review if is needed to change the Readme.md
• Ensure new entries are added to CHANGELOG.md, if applicable.

SDK/CLI

• Are there new checks included in this PR? No

UI

• All issue/task requirements work as expected on the UI
• If this PR adds or updates npm dependencies, include package-health evidence (maintenance, popularity, known vulnerabilities, license, release age) and explain why existing/native alternatives are insufficient.
• Screenshots/Video of the functionality flow (if applicable) - Mobile (X < 640px) — N/A (config-only, no UI changes)
• Screenshots/Video of the functionality flow (if applicable) - Table (640px > X < 1024px) — N/A (config-only, no UI changes)
• Screenshots/Video of the functionality flow (if applicable) - Desktop (X > 1024px) — N/A (config-only, no UI changes)
• Ensure new entries are added to CHANGELOG.md, if applicable.

API

• All issue/task requirements work as expected on the API — N/A
• Endpoint response output (if applicable) — N/A
• EXPLAIN ANALYZE output for new/modified queries or indexes (if applicable) — N/A
• Performance test results (if applicable) — N/A
• Any other relevant evidence of the implementation (if applicable) — N/A
• Verify if API specs need to be regenerated. — N/A
• Check if version updates are required (e.g., specs, uv, etc.). — N/A
• Ensure new entries are added to CHANGELOG.md, if applicable. — N/A

License

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[ghost]

🔒 osv-scanner: 2 finding(s) in ui/pnpm-lock.yaml

Severity gate: HIGH,CRITICAL,UNKNOWN

Severity	ID	Package	Version	Summary
🟠 HIGH (7.5)	GHSA-w5hq-g745-h8pq	npm/uuid	10.0.0	uuid: Missing buffer bounds check in v3/v5/v6 when buf is provided
🟠 HIGH (7.5)	GHSA-w5hq-g745-h8pq	npm/uuid	9.0.1	uuid: Missing buffer bounds check in v3/v5/v6 when buf is provided

To accept a finding, add an [[IgnoredVulns]] entry to osv-scanner.toml at the repo root with a reason and ignoreUntil.

_{View run}

[ghost]

✅ Conflict Markers Resolved

All conflict markers have been successfully resolved in this pull request.

[ghost]

✅ All necessary CHANGELOG.md files have been updated.

[ghost]

🔒 Container Security Scan

Image: prowler-ui:72a7939
Last scan: 2026-05-25 11:57:52 UTC

📊 Vulnerability Summary

Severity	Count
🔴 Critical	2
Total	2

2 package(s) affected

⚠️ Action Required

Critical severity vulnerabilities detected. These should be addressed before merging:

• Review the detailed scan results
• Update affected packages to patched versions
• Consider using a different base image if updates are unavailable

---

📋 Resources:

• Download full report (see artifacts)
• View in Security tab
• Scanned with Trivy

[Alan-TheGentleman]

Maybe we can use this opportunity to remove this kind of imports (import React)