Add git history to pages

[peytondmurray]

Summary

This PR adds git history to pages. Since I'm also adding in a little js to handle some clicks, I also added configs for prettier and eslint. To build we now need pandas (for rendering tables of git data) and gitpython (for fetching git history).

The git history button is in the right hand sidebar. It opens up a modal with a table of edits to the current page; git history is fetched at build time.

The way it works is that the "Show article history" button is actually a checkbox which toggles its state. When it's checked, the modal is shown with a CSS rule; otherwise the modal is hidden.

Changes

• Added prettier and eslint configs
• Added pandas and gitpython dependencies
• Added template for rendering git history. The template is inserted into the right hand (secondary) sidebar

Notes

I considered using the bootstrap.js modal, but to be honest I was never able to get this to render properly (always showed up underneath the top nav bar), and the modal background itself always appeared above the dialog box, so you could never close it. Generally speaking the bootstrap.js components haven't been very easy to use with sphinx/pydata-sphinx-theme, and this was definitely a case where it was easier to roll my own modal.

Here's what it looks like:

Resolves #21.

[random-person-001]

Would the intended user more likely wish to see the rendered page at that historical point in time, or the source code changes with that commit?

I am not sure myself. If we wanted a (mostly-correctly) rendered page at that point in time, we could point to ex
https://github.com/observational-dev/oawiki/blob/ff553518ef0921871c7216f41873aa79e70ff8e8/src/other/examplepage.md
where we currently point to
ff55351

Overall, thank you for the excellent feature, looks great!

[random-person-001]

Looks good; I just have the user question of whether someone looking through this is more likely to be interested in the source changes at that edit, or a rendered snapshot of the page at that point in time. Which I don't know the answer to

[peytondmurray]

Well, if they're digging that hard they can always reach out to wiki stooges for help understanding what they're looking at. Sadly github's markdown renderer won't handle any of the markdown extensions provided by myst-parser, so output will likely be somewhat garbled. I vote to keep it as is.