Enable no-unused-imports lint rule

Description

Enable a lint rule to automatically detect and flag unused imports across the codebase.

Problem

During code refactoring and development, unused imports can accumulate, leading to:

• Increased bundle size
• Code clutter and reduced readability
• Potential confusion about actual dependencies
• Maintenance overhead

Proposed Solution

Enable the no-unused-imports or similar lint rule in our ESLint configuration to automatically detect and flag unused imports.

Implementation Options

1. ESLint rule: Enable @typescript-eslint/no-unused-vars with import-specific configuration
2. Additional tooling: Consider tools like eslint-plugin-unused-imports for more specific unused import detection
3. Auto-fix: Configure the rule to automatically remove unused imports where safe

Acceptance Criteria

• Lint rule is configured in .eslintrc.js or equivalent config file
• Rule catches unused imports in TypeScript/JavaScript files
• CI pipeline fails if unused imports are detected
• Documentation updated with information about the new rule
• Existing unused imports in codebase are cleaned up (separate task/PR)

Additional Notes

This will help maintain code quality and prevent accumulation of dead imports during ongoing development and refactoring work.

Start by locating the ESLint configuration, such as .eslintrc.js or its equivalent, and the CI pipeline that runs linting. Compare the available unused-import rule options for TypeScript and JavaScript, then verify that the selected rule is enforced in CI and that the documentation describes it; existing unused-import cleanup is explicitly separate.