release: create a relui workflow for the vscode-go release process

[hyangah]

This issue tracks the relui workflow to further automate the vscode-go release process.
The new relui-based release process includes

• Sanity check on the version

• Stable release: the initial version will simply migrate the existing release process.
  But the final version will handle:

  • Create an issue to track the release
  • Create a new release branch (for v0.M.0) from the chosen prerelease version.
  • Create CLs for cherry-pick (for v0.M.N where N > 0).
  • Create a CL to update the version in package.json and package-lock.json.
  • Create a CL to add/update extension/LICENSE file. (not the top-level LICENSE file).
  • Tag the release candidate.
  • Wait for the operator's manual testing with RC.
  • Trigger the next prerelease for v0.(M+1).0.
  • Tag the final release.

• Prerelease (to be added with golang/vscode-go#1935)

  • Work with the master branch (no new branch creation)
  • Create a CL to update the version in package.json and package-lock.json.
  • Skip processes like issue/milestone creation.

cc @h9jiang

[h9jiang]

As the first CL, we will create a new workflow which is responsible of creating a release candidate for the stable version of vscode-go extension.

The input version should be the next version of some existing versions. The input version has to be a stable version. The input version's pre-release label should be empty. (The flow will figure out which rc it will pick)

[gopherbot]

Change https://go.dev/cl/607176 mentions this issue: internal/task: add new workflow for vscode-go pre-release

[h9jiang]

Some offline sync with Hana and Dmitri, we want to adopt the approve functionality same as gopls release automation. And also use the cool drop down menu.

The input of the release will be simplifies as below, the coordinator only need to provide what kind of version he/she want to release. Right now, it can only be next minor or next patch.

The flow will figure out the version based on the user input, the local relui below, I choose next minor. The relui return v0.44.0-rc.1 WAI.

Some more explanation, right now, the latest release is vscode-go is v0.42.0. The next stable version should be v0.44.0 because 0.43 will be a insider version.

The local relui below, I choose next patch., the relui return v0.42.1-rc.1. The next patch version is v0.42.1 and the pre-release version start with rc.1. (because there is no other rc available)

@hyangah @dmitshur

And the same input will be applied to gopls release as well, the coordinator will no longer need to put the version string. The screenshot in this comment should give you an earlier taste what will be coming in gopls. @findleyr

[h9jiang]

The next CL, we will add a step in gopls release process. Every gopls release will trigger a gopls version update in vscode-go repo.

The update will happen at the last step of gopls release & gopls pre-release.

[gopherbot]

Change https://go.dev/cl/608416 mentions this issue: internal/task: add step to update gopls version in vscode-go project

[h9jiang]

Next CL, the flow will create the release milestone and release issue. (only if there isn't one already created and open)

The first run of the flow create this release issue below and add it to the release milestone.

The second time, it realize there is an existing & open issue, so it will not create this issue again.