[QOL] - ESLint on save

[kevin-pierce]

This is simply a minor QoL upgrade ; with these changes, ESLint should now run on-save (for anyone using VSCode). Initially, this might cause some ugly diffs in your files (due to the restructuring of imports) but hopefully this makes linting a little less annoying going forward.

Checklist

• My PR name is descriptive and in imperative tense
• My commit messages are descriptive and in imperative tense. My commits are atomic and trivial commits are squashed or fixup'd into non-trivial commits
• I have run the appropriate linter(s)
• I have requested a review from the PL, as well as other devs who have background knowledge on this PR or who will be building on top of this PR
• If I have made API changes, I have updated the REST API Docs
• IF I have made changes to the db/models, I have updated the Data Models Page
• I have updated other Docs as needed

[connor-bechthold]

I'm not too familiar with this but couple of things

• If we do this we should probably include all the reformatting that's done because this is going to bloat future PR's
• Also just realized, the linter that we typically run is through yarn, and not ESlint. Curious why we have both? If the yarn linter works for us now, we can probably stick with that instead of going through the hassle of reformatting things