Release Drafter: update config after v1.0.0 is released

[stephiescastle]

From our docs:

Temporary beta release considerations

This includes a temporary override (in .github/workflows/update-release-draft.yml) of the default versioning/tagging process (configured in .github/release-drafter.config.yml), because Release Drafter doesn't yet support incrementing prerelease versions (see open issue). We will need to manually update the release title and tag prior to publishing it, at least until we get to 1.0.0 final. At that point, if we remove the override, it should automatically figure out the next version number, according to how the PRs since the previous release have been tagged as major/minor/patch.