Use annotated tags for releases

[SeanTAllen]

The X.Y.Z tag will live on. Use an annotated tag as they can be signed.

From the documentation:

Annotated tags, however, are stored as full objects in the Git database.
They’re checksummed; contain the tagger name, email, and date; have a
tagging message; and can be signed and verified with GNU Privacy Guard
(GPG). It’s generally recommended that you create annotated tags so you
can have all this information; but if you want a temporary tag or for
some reason don’t want to keep the other information, lightweight tags
are available too.

[ponylang-main]

Hi @SeanTAllen,

The changelog - changed label was added to this pull request; all PRs with a changelog label need to have release notes included as part of the PR. If you haven't added release notes already, please do.

Release notes are added by creating a uniquely named file in the .release-notes directory. We suggest you call the file 30.md to match the number of this pull request.

The basic format of the release notes (using markdown) should be:

## Title

End user description of changes, why it's important,
problems it solves etc.

If a breaking change, make sure to include 1 or more
examples what code would look like prior to this change
and how to update it to work after this change.

Thanks.