Analyze files for unused imports and remove them

[sridmad]

Bug Description

Many source files in the repository may have unused import statements, leading to increased bundle size, reduced clarity, and possible issues with tree-shaking or static analysis tools. These can also cause confusion for contributors reviewing code, making maintenance harder.

Reproduction Steps

• Open multiple TypeScript/JavaScript files in the repo.
• Observe that some imported modules/functions/types/constants are not referenced anywhere else in the file.

Expected Behavior

• All import statements should correspond to usage within the file.
• Files should not contain imports for unused modules, functions, or types.

Impact

• Affects code clarity, maintainability, and could bloat builds.
• Automated static analysis (e.g., ESLint, ts-unused-exports) may fail or produce warnings.

Proposed Solution

• Audit TypeScript and JavaScript files with static analysis tools (such as ESLint --no-unused-vars, ts-unused-exports, or similar).
• Remove any unused imports in all affected files.
• Optionally, add automated lint rules/checks to catch unused imports on future PRs or commits.

Additional Context

• Applies to all source code files in the project (especially .ts, .tsx, .js, .jsx).
• Example (incorrect):

import { rarelyUsed } from './utils';
// ...

• Example (correct):

// No unused imports