New git workflow

[IamTheCarl]

That last update took a long time, even if it wasn't a ton of content. A lot of that time was spent experimenting, figuring out the best way to bring mutable data, and also with my day job since it sometimes requires me to work overtime.

I would like to make the workflow more properly defined in some ways, and more loose in others.

I want to make the following changes:

• Not every commit to the master branch should be a release
  • We'll have tags for the commits that are releases
• The master branch should be protected
• CI pipelines should automatically test source code and automatically build and publish release builds

This will take some work to get started, so here's a checklist:

• [x] Protect the master branch
• [x] Setup CI for merging into master
  • [x] rustfmt
  • [x] clippy
  • [x] cargo test
• [ ] Setup CI for publishing
  • [ ] Setup Linux build
  • [ ] Setup Windows build

The only question is if I should use Github's free git runner hours or if I should use my own server. That server has plenty of throughput available so I'm leaning toward using that, since it'll never run out.

[IamTheCarl]

Merge CI was implemented here: https://github.com/IamTheCarl/CommandCAD/pull/7