Make the release script more robust

[bwagner5]

What version of Hugo are you using (hugo version)?

v0.97.0

Does this issue reproduce with the latest release?

Yes

When installing v0.97.0 w/ go install w/o the google go proxy, a checksum mismatch occurs.

$ go clean -modcache
$ GOPROXY=direct go install github.com/gohugoio/hugo@v0.97.0+extended
go: downloading github.com/gohugoio/hugo v0.97.0
go: github.com/gohugoio/hugo@v0.97.0+extended: github.com/gohugoio/hugo@v0.97.0: verifying module: checksum mismatch
	downloaded: h1:VkjBIIADmPnxhA9t4XhNuH2H/U8fg5u5G3dsvS3jBBk=
	sum.golang.org: h1:cKR421+00hzlh8H5ckmtkWAZbKjIT7hDPY7h/DXEQiI=

SECURITY ERROR
This download does NOT match the one reported by the checksum server.
The bits may have been replaced on the origin server, or an attacker may
have intercepted the download attempt.

[bep]

This will fix itself with the next Hugo release. If you want it fixed sooner, you may want to talk to the maintainers of the gosum db that has the wrong version registered (admittengly due to me having to start over the release twice because of tech failures).

[bep]

Since we don't have any "edit release notes step" in the release notes script anymore, we could probably delay the creating of the release on GitHub (with the tag) until after we have built all the binaries (which is where it failed in this scenario).