chore: pre-commit hooks for code style and commit message quality

[hydrosquall]

Motivation

• Generating quality changelogs for [ci] Add auto to manage versions, changelog, and deployment to NPM #63 requires consistently formatted commit messages. This is something a script can check more reliably / consistently than a person.
• More context from elsewhere in the nteract ecosystem: Updates on repo release workflow nteract#5568 (comment)

Changes

• Mimic the setup from @captainsafia in chore: fix up commit-related linting tasks nteract#5567
• Sets up Prettier in this repository (we had a .prettierrc file, but it wasn't actually being used)

Testing

• I wrote several non-compliant commit messages , and was warned with information about what needed to be fixed in the message before they'd be accepted. Here's an example of how it looks when a stray capital letter finds its way in : https://a.cl.ly/eDuynZmj
  

Notes

• Setting up prettier with Husky: https://prettier.io/docs/en/precommit.html#option-1-lint-stagedhttpsgithubcomokonetlint-staged
• Option for the future: We can add tooling to help people write linter-friendly commit messages, just didn't want to change too many things at once https://github.com/commitizen/cz-cli

[willingc]

Nice @hydrosquall! I'll leave it for you to merge because I don't want to accidentally trigger a release.

[hydrosquall]

@willingc thank you!

And not to worry, a release should only be triggered if we explicitly attach a Github release label to this PR (but we'll see momentarily whether this was set up correctly :).

[github-actions]

🚀 PR was released in v8.2.12 🚀