build: lint JS in Markdown

[dsanders11]

Mostly whitespace, semis, and commas, but it did catch a couple of spots where there were mistakes with brackets, and did identify some code blocks that were using javascript when they should be using json for the language identifier.

Also threw in some changes from json to jsonc for language identifier when comments were present, as it is still recognized by GitHub and prevents the nasty dark red text background when viewing the code on GitHub.

[malept]

I wonder if it is worth running something like a daily / weekly GitHub Action to execute prettier / lint-roller or something on the repo.

[dsanders11]

Ah, I assume you mean to clean up the changes that come in from GitBook? Good point, those bypass any kind of linting requirement unfortunately. We probably should, although I remember it being a bit of a pain to do commits from a GitHub Action workflow. Will explore doing so in a future PR.

[dsanders11]

I wonder if it is worth running something like a daily / weekly GitHub Action to execute prettier / lint-roller or something on the repo.

Paper-trailing, there's now an auto-fix workflow that runs on pushes to fix things coming in from GitBook when possible, via #151.