Documentation overhaul - Fixing formatting issues, autodoc implementation, and added variables for versions. (#3734)

Closes #3639. 

This is a bit of an overhaul of the docs to make them more
easy to utilize. This changes include:
- Removal of overhanging public aspects of the documentation
- Reformatting of terminal commands to allow for easy copy & pasting
- Updating points of contact
- Screenshot Updates
- Automated code API documentation. [Google's docstring
style](https://github.com/google/styleguide/blob/gh-pages/pyguide.md#38-comments-and-docstrings)
should be used.
- Added variables for things like software versions & packages.
- Unless python & node version are manually specified, when docs are
built these will be pulled from
[`.nvmrc`](https://github.com/HyphaApp/hypha/blob/main/.nvmrc) &
[`.python-version`](https://github.com/HyphaApp/hypha/blob/main/.python-version)
- Consolidated the production and development guides into one location
(both under `Setup` rather than one under `Getting Started` and one
under `Setup`), and updated them to be similar to one another.
- Added different steps for getting Hypha development deployed under
multiple OSs

- Keeps the migrations to delete the public tables
- Updates and adds a global footer (admin configurable)
- Update the layout of homepage

Fixes #3110 #3559


## Test Steps

- [ ] Remove the public site, go to "Wagtail Admin" > "Pages", set the
"Apply Home Page" as the default page of the site. Remove the public
site page
 - [ ] Do regression of the whole site

---------

Co-authored-by: Wes Appler <wes@opentech.fund>

Also, removes breadcrumbs and StoryBock

Depends on #3720

closes #3080

The images are linked relative to page now. This prevents the mkdocs
warnings and also let these images render itself nicely inside the
editor or github interface.

This way of referencing also helps for future if the docs get deployed
to a path instead of a top-level domain

- Add black, djhtml, prettier
- Add precommit


This PR add configurations for black, djhtml and prettier.

- black is used for formatting python files
- djhtml for formatting html files. Use `{# fmt: off #}` and `{# fmt: on
#}` where needed.
- prettier for formatting of sass,css,yml and js files

Note: prettier picks up some of it's config from `.editorconfig`, so
it's updated appropriately

Formating of mardown files, minified or vendored js files are ignored.

Formatting used off-the-self rules for better consistency with the
community as large.

The formatting is not applied to all the files as it will introduce a
lot of merge conflict with
current PRs, instead `pre-commit` config is provide which can be
installed by `precommit install`
locally. It will format only the modified files in the PR/commits. 

Once majority of the current active PRs are either rebased & formatted
using precommit or merged, we can
run the `make fmt` on the full repo and activate additional prettier and
black checks in our lint rules.

The modified sass files fixes the eslint error that would came up if we
were to apply the prettier formatter on them.

Fixes #3500

When following docs to set up a development environment, without this
change one would see this error:

> Unknown command: 'wagtailupdatesite'. Did you mean
> wagtail_update_index?

Fixes: #3112

---------

Co-authored-by: Saurabh Kumar <theskumar@users.noreply.github.com>

Run Django and docs preview server, and watch and compile frontend
changes in parallel.

This lets you quickly spin up and run everything in a single terminal.

Fixes #3242

Fixes: #3250

- Add page last edited info on each page
- Update header - site title, repo name & icon
- Disable custom fonts, use system-fonts
- Add copyright info in footer
- Update navigation structure and behaviour
- Add source code view and edit buttons
- Refractor documentation