Retag v0.14 as v0.14.0 to strictly follow semver

[shreyb]

A number of go tools in the go ecosystem, like pkg.go.dev, don't work unless you have a strict semver version number, which requires a patch version for each. To make this work properly, we'll have to do the following:

• [x] New github action that, upon a new tag being generated, runs curl https://sum.golang.org/lookup/github.com/fermitools/managed-tokens@$VERSION, e.g. curl https://sum.golang.org/lookup/github.com/fermitools/managed-tokens@v0.11.1 and throws away the result
• [x] Cut v0.14.1 with this change
• [x] Verify the result on https://pkg.go.dev/github.com/fermitools/managed-tokens

[shreyb]

Looks good. The new package shows up on pkg.go.dev