Investigate using code mods to resolve different types of linting errors

[JackHaeg]

Overview

As part of the broader effort to fix linting errors across the VRMS codebase, we need to assess whether code mods can be used to efficiently resolve certain types of errors. The goal is to identify which linting rules are good candidates for automated fixes.

Action Items

• [ ] Audit the current linting errors across the codebase using yarn lint.
• [ ] Categorize common error types (e.g., missing semicolons, unused imports, incorrect spacing, etc.).
• [ ] Research available tools such as eslint --fix, jscodeshift, and ts-migrate to determine coverage and limitations.
• [ ] Create a summary of which linting errors can be safely auto-fixed and which will require manual review.
• [ ] Share findings with the team to inform the linting remediation plan (paste as a comment).
• [ ] Paste approved code mod instructions as a comment on #1969
• [ ] Close this issue as complete

Resources/Instructions

• ESLint CLI Docs – --fix
• jscodeshift – Facebook's codemod tool
• ts-migrate – Airbnb’s TypeScript migration tool
• This issue is part of the epic: #1966