Update gha release

[jmctune]

The idea here is:

• Any commits to main will build a "dev" version of the current tag
  • If we are on tag v4.0.0, a commit to main will make a pre-release and tag for v4.0.0-dev
  • This was changed from automatically converting to v4.1.0 because this assumes the next tag already. We don't know what the next version will immediately be.
• Any existing assets attached to the dev release will be deleted and the latest zip will be attached instead
• When a new tag is pushed to the repository, the same tag (minus the v) will be written to the version.update file and committed
• We move the tag to the commit that made the change to version.updateso so that the tag includes the version bump
• This also kicks off a new official release with the tag that was pushed

It's similar to before, but there is no more PR -> dev -> main workflow. It's just PR -> main. main will act as dev until it has been tagged, which will then turn into a release. PRs shouldn't make their way into main without testing and there shouldn't be any direct pushes to main without going through a PR first.