Added some basic project governance docs

[mwheeler]

This PR adds the basic project governance docs you'd expect a project to have, specifically:

1. A general contribution guide
2. A code contribution guide (references code quality/standards and PR process)
3. A PR guide (that puts in writing our 2 developer 2 approval minimum standard)
4. A coding standard (intentionally kept very minimal since we try to stick to PEP-8, smaller is easier to remember and enforce)

Note: It's written in a future-facing capacity assuming we have open sourced and thus have Github Actions setup to prevent PRs from merging if linting or unit testing fails (this is not currently the case, but it is the intended end goal for our QA standards once we open source)

Edit: This addresses #356 (which ironically didn't exist before starting this work, contrary to the guides! for some reason I thought the other documentation issue we had open also covered these governance docs)

[mwheeler]

Looks good, most comments are typos. I think the content is complete.

One question, do we want to include newlines at the end of text files?

Fixed in all current issues in ec55731

As for the newlines at end of text file... that's already a PEP-8 thing (also, technically - text files by definition "must" have a newline at the end of every line in unix terms, not sure if windows shares this) - there's even some old school programs that won't work properly w/o newlines at the end of text files (though they're becoming rarer and rarer)