ci(release/go): add Go Binding release

[yuchanns]

Part of #4892.

[Xuanwo]

Problem Hitted: The ASF doesn't allow us to create Fine-grained personal access tokens. And Personal access token (classic) requires the Full control of private repositories permissions.

Although I trust all OpenDAL PMC members, I still feel uncomfortable generating and sharing such a token in 1Password.

Do we have other choices?

[yuchanns]

Can we use Github Secrets instead?

[Xuanwo]

Can we use Github Secrets instead?

No differences for that.

---

How about use schedule with cron in opendal-go-services instead? We can pull opendal tags every five mintues, and build if new tags happend.

[yuchanns]

I'll take a try.

[Xuanwo]

I'll take a try.

Sorry for the inconvenience and thank you for your patience.

[yuchanns]

The part about releasing services has been moved to apache/opendal-go-services#9.

[Xuanwo]

Hi, I believe this action is unnecessary. Tags in OpenDAL can be created directly by the release manager. We just need to update the release document on how to release the Go binding.

[yuchanns]

Alright. I'm just not familiar with the release process of Apache products. I'll close this PR.

We just need to update the release document on how to release the Go binding.

It's your control now. :)

[Xuanwo]

Alright. I'm just not familiar with the release process of Apache products. I'll close this PR.

Releasing is the most important thing of the ASF. Are you interested in becoming our next release manager who will release first version of go binding? I'm willing to provide help you need.

[yuchanns]

Sorry, but I'm not interested in release. I think it is better to have you leading the version release.

I would like to answer any questions if you encounter issues in release go.