Ci/Setup Linting

[AlexKMarshall]

This sets up linting on the React side. Mainly following information from https://www.robertcooper.me/using-eslint-and-prettier-in-a-typescript-project and facebook/create-react-app#8849

Add the following to your VSCode settings.json file to automatically apply linter fixes when you save files

{
  "editor.codeActionsOnSave": {
    "source.fixAll.eslint": true
  },
}

Note that the .env file for the client side is committed to the repo as described at https://create-react-app.dev/docs/adding-custom-environment-variables/

Secret variables must not be added to this file, as they will be visible in the final build of the client.

This PR also adds a pre-commit hook to run the linter. It will fix automatically any files it can, but anything that it can't fix automatically will cause the commit to fail until you fix them manually.

Additionally, I had to set up lint-staged differently because of running two separate packages, client and server. I followed instructions at https://github.com/sudo-suhas/lint-staged-multi-pkg

[codecov-commenter]

Codecov Report

Merging #16 into master will increase coverage by 47.72%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master      #16       +/-   ##
===========================================
+ Coverage    2.27%   50.00%   +47.72%     
===========================================
  Files           3        2        -1     
  Lines          44        2       -42     
  Branches       12        0       -12     
===========================================
  Hits            1        1               
+ Misses         43        1       -42     

Impacted Files	Coverage Δ
client/src/App.tsx	100.00% <ø> (ø)
client/src/index.tsx	0.00% <ø> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9833de4...1ef0fd9. Read the comment docs.