x/tools/gopls: generate GitHub release as part of release automation #76869
Description
Historically we would edit gopls release notes during the release process, using the GitHub releases feature and its Markdown editor (which weirdly differs from normal GitHub-flavored markdown). Now that gopls has its own doc site at https://go.dev/gopls, release notes (example) are mostly written as we contribute features, by including x/tools/gopls/doc/release/v0.*.md files in the same CL, which is much smoother.
At this point, the GH release mechanism is essentially redundant. So we have a choice to make between stopping using it entirely, or developing our release automation scripts to update the GH release notes based on the canonical release notes.
Pros of keeping GH release notes:
- it's a place for us to mention contributors (though we could do this in the canonical release notes too).
- it's a place for users to express their feelings about the release with emojis (though it's fair to say that, though we love positive vibes, there's not much actionable signal here compared to, say, GH issue voting).
Cons:
- one-time work of updating the automation.
- confusion about which features of GH the Go project relies on and which are merely mirrors.
Thoughts? Emoji-vote away. ;-)