Make the pre-commit hook fix formatting

[kienstra]

Changes

• The pre-commit hook is now like Gutenberg's. It fixes formatting when possible and stages the fix before the commit. If it can't fix it, it blocks the commit.
• Removes the husky pre-commit hook package. It was outdated, so we either had to migrate or remove it.
• So to avoid husky, this adds the pre-commit hook with a git command in package.json prepare
• I'll still have to iterate on this. But maybe we could use this in other repos if it helps.

Testing instructions

1. Do a fresh clone of this repo
2. git checkout remove/husky
3. composer i && nvm use && npm i
4. Create a JS formatting error. Maybe remove a space inside parentheses in a JS file.
5. Stage that change
6. git commit -m "Should be fixed"
7. Expected: That formatting error is fixed before being committed.

[kienstra]

This won't always work, but I like it more than importing husky and updating its versions.

Also, we won't need a .husky/ directory, only .githooks/.

I don't like directories named after vendors, but we still have some.

[kienstra]

There aren't this many commits for this work, those are because this PR targeted another branch, and I merged that branch in.

[kienstra]

Sorry, this actually isn't ready for review. It has some bugs.

[kienstra]

Not related, I just wanted to indent this with tabs, like phpcs.xml

[kienstra]

This PR din't have that many commits

Those are because this was branched off another PR, and I merged that in.

[kienstra]

To make linting pass

[kienstra]

Sorry, this is ready for review again.

[kienstra]

Sorry for yet another GCB PR!

[mike-day]

This is working well, @kienstra! It's a nice touch to do this without relying on husky.

---

Before making the commit, I had linting errors:

---

After making the commit, the auto-fixable errors were all fixed and the commit succeeded:

[kienstra]

Hi @mike-day,
Wow, great to see how it fixed those linting errors on your machine!

Thanks for the screenshots and for testing this.