Decide on dev version protocol

Currently, our version bump workflow only supports creating a dev version on a patch (e.g. 1.0.1 -> 1.0.2.dev0 -> 1.0.2). However, there may be cases where we want to create a dev version on a minor/major version (e.g. 1.0.1 -> 2.0.0.dev0 -> 2.0.0).

After some discussion, we have two options:

**Option 1**
Give up on automating version bumping via workflows, and instead just create the bumps manually.

Steps:
- Finish up work for a new version, merge changes to main
- Create a version bump branch from main
- Run bumpver
- PR changes back into main

**Option 2**
Continue doing version bumps via a workflow, but cope with some weirdness.

We would need a way to create a dev version on a new patch, major, or minor version. We would need a way to increment that dev version. And we would need a way to finalize (i.e. remove) that dev version. These could be a series of checkboxes, but unfortunately GH actions does not allow me to disable different parts of the workflow inputs based on current state. This means we would need to decide what it means (or just throw an error) if a request comes in that wants to both increment and finalize a dev version, or create a new patch version without finalizing the dev version first. Basically, we would just have a lot of error cases possible here.

Steps:
- Finish up work for a new version, merge changes to main
- Run the bump version workflow