'Release' Branching for CI/CD and Contributions

As an Open Source project we want to avoid having branches "compete" for who gets to be the development deployment at https://devstore.rerum.io/v1/.

We hope for many PRs to come in at once from Open Source contributors.

We imagine a future where RERUM is a kind of "download and install" package.

A `release` branching mechanic that helps control when the _production_ and _development_ deployments occur is necessary in order to help the current situation with "competing" PRs and should be forward thinking for the ways in which we imagine making RERUM code available to the public.