Write CONTRIBUTING.md

[ryanrolds]

• Include the link to Discord.
• Encourage people to talk with us in discord before submitting PRs.
• Outline how to start the services from the root as well as how to start them in each of the subdirs.
• Include instructions on how to run tests and linters from root and subdirs.
• Master on the main repo is assumed to be stable at all times
• Everyone works in branches (on a fork or not - personal preference thing)
• PRs that are not ready to review are kept in the "Draft" state (it is possible to switch a non-draft to a draft - there is a button under the review list in the PR).
• PRs that are not in a Draft state read ready to be reviewed
• At least one review is required to merge, but large PRs or PRs making arch changes should consider getting at least 2 reviewers
• All PRs should include reasonable test coverage is the changes are setup for tests
• Linting must pass
• Once approved by reviewer(s), the author merges to master(edited)
• Work should have a related ticket, which holds the conversation about the work