Automate our branch strategy for hot fixing

Hot fixing needs to be done urgently when it's done.

Our current hot-fix release protocol:

- Once feature is identified, notify support team about issue so they can respond to it appropriately and create auto-replies and documentation.
- Create branch of `master`, since it reflects what is in production.
- Fix issue on branch.
- PR fix against master (this PR may include the patch version bump to reduce overhead)
- Once fix is verified by another team member, proceed to publishing process.
- After publishing, merge master into the active develop branch.

The branch & PR portions of this should be automated.