Implement code mods to resolve eligible linting errors

### Dependency
- [x] #1967

### Overview
Following the investigation into using code mods for linting errors, this task focuses on implementing those fixes across the VRMS codebase. The goal is to automate resolution of the errors identified as safe to auto-fix, streamlining the larger lint cleanup effort.

### Action Items
- [ ] Review the output from the investigation documented in #1967
- [ ] Implement code mods suggested in #1967
- [ ] Create individual issues for each code mode and paste issues below (so that each mod can have a PR):
- [ ] [_Example issue 1_]
- [ ] Run code mods in batches, verifying that no unintended changes are introduced.
- [ ] Commit and push fixes incrementally to avoid overwhelming code reviewers or creating large merge conflicts.
- [ ] Coordinate with the team if the changes will affect shared files or ongoing branches.
- [ ] Document which errors were resolved by automation for future reference.

### Resources/Instructions
- Refer to tool setup guides:
- [ESLint Auto-Fix](https://eslint.org/docs/latest/use/command-line-interface#--fix)
- [jscodeshift](https://github.com/facebook/jscodeshift)
- Reuse any helper scripts created during the investigation phase.
- Consider opening a draft PR to preview the scale and type of changes before merging.
- This issue is part of the epic: #1966