docs: initialize mkdocs config and workflow for github pages

[gvauter]

Description

Adding initial mkdocs-material files for repo documentation. The mkdocs content will be published to Github pages. Future pull requests will update and create the Markdown content for publishing.

Type of change

• New feature (non-breaking change which adds functionality)

How has this been tested?

• Tested in fork

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[jpower432]

Looks good. Only one change requested on the workflow.

[jpower432]

These should be pinned to hashes for consistency. Implemented here -#242. Realizing that this should be added to the contributing guide with suggested tools.

[jpower432]

Issue added here to make sure the docs are updated #317

[jpower432]

LGTM