Fix lint-staged configuration

[macfarlandian]

Description of the change

husky and lint-staged are a bit finicky about how they are used inside of a monorepo since they interact with both your npm package and your git repo, and after a few lint errors slipped through to CI I realized that the linters weren't actually running properly inside the husky pre-commit hook. Pushing the lint-staged configuration down to the individual packages, as recommended here (and referenced from the official lint-staged docs), should fix this. It makes for a bit more redundant configuration but it doesn't really seem like there's a better alternative!

Type of change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Configuration change (adjusts configuration to achieve some end related to functionality, development, performance, or security)

Related issues

Closes #239

Checklists

Development

These boxes should be checked by the submitter prior to merging:

• Manual testing against realistic data has been performed locally

Code review

These boxes should be checked by reviewers prior to merging:

• This pull request has a descriptive title and information useful to a reviewer
• This pull request has been moved out of a Draft state, has no "Work In Progress" label, and has assigned reviewers
• Potential security implications or infrastructural changes have been considered, if relevant

[coveralls]

Pull Request Test Coverage Report for Build 334365679

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 5.164%

---

Totals
Change from base Build 320690911:	0.0%
Covered Lines:	60
Relevant Lines:	1390

---

💛 - Coveralls

[jessex]

I don't know a better alternative either 👍

[jovergaag]

This is what we're doing in pulse-dashboard as well.