Solve ESLint Errors Across Codebase

[zzadxz]

Description:
As a developer, I want to resolve existing ESLint errors in the codebase to maintain a clean and consistent code structure, improve readability, and adhere to best practices.

Acceptance Criteria:

1. All current ESLint errors and warnings are reviewed and resolved, specifically addressing:
   • Unused variables (e.g., @typescript-eslint/no-unused-vars)
   • Console statements (no-console rule)
   • Missing key prop in lists (react/jsx-key)
   • Usage of <img> tag instead of <Image /> in Next.js (@next/next/no-img-element)
   • Unescaped entities in JSX (react/no-unescaped-entities)
2. Update the ESLint configuration to ignore specific rules in testing files (e.g., allow console.log statements and unused variables in tests).
3. Ensure that logging is conditionally enabled only in development environments using a custom logging utility function.
4. All fixes should be committed, and code should pass the ESLint check without errors or warnings.

Tasks:

• [ ] Identify and document all ESLint errors in the codebase.
• [ ] Refactor code to resolve unused variables and other warnings.
• [ ] Replace console.log statements with a custom logging utility.
• [ ] Add key props to all elements in iterators.
• [ ] Replace <img> tags with Next.js <Image /> component.
• [ ] Escape all unescaped entities in JSX.
• [ ] Update .eslintrc.json to handle testing-specific rule exceptions.
• [ ] Run npm run lint -- --fix to auto-fix where possible and verify changes.

Project: RATTM Roadmap

Priority: High

[zzadxz]

Resolved in #56, closing