Enforce eslint and prettier rules with a pre-commit hook

[tpadjen]

Dsecription

Adds a pre-commit hook using husky that auto-fixes eslint errors and prettifies staged files in case a contributer does not have their IDE configured to run those actions on save.

When Commits Fail

This may occasionally cause a commit to fail when the eslint problem is not auto-fixable.

Usually this is because of an important web standard violation, such as a missing alt description on an <img /> tag. In these cases, simply clean up the problem, add the change to staging, and re-commit.

If the error is more involved or less useful, consider turning off the associated eslint rule in .eslintrc.json, like so:

"rules": {
    "@next/next/no-img-element": "off",
    // ...
}

If you absolutely need to make a commit, linting be damned, you can add the --no-verify option to your git commit command. Because this is possible, linting enforcement can possibly be moved to CI once a deployment pipeline has been established.

Other Changes

This also cleans up some eslint errors/warnings concerning missing alt tags and unescaped html entities.

[samholmes]

@tpadjen I didn't notice this PR when I worked on #13

Could you diff this PR with your work to see whether there are any changes you'd recommend in addition? A review of my work so to speak.

[samholmes]

Overall, these seem like good additions. Could you rebase this PR on to main (master), and then rename the PR to "Linting additions". Thanks! 🙌

[samholmes]

I prefer to use the prettier ESLint plugin for formatting so that way eslint --fix applies the linting fixes in addition to the formatting errors all in one go. A dev can use an eslint IDE integration to get auto formatting and linting fixes on file save.

[samholmes]

I think I resolved this same issue in my PR, but instead of factoring out the string, I kept it inline. That'd be preferable since this consts is single-use.

[samholmes]

This is useful to remove the warnings.

[samholmes]

I'm unsure what this fixes.