Trigger release workflow manually

[yixinglu]

What type of PR is this?

• bug
• feature
• enhancement

What problem(s) does this PR solve?

Issue(s) number:

close #3815

Description:

when releasing a nebula PATCH version(z version of x.y.z), create git tag on one same branch rather than a new branch, such as:

release-3.2   -----+----------+------- branch
                    \          \
                    v3.2.0    v3.2.1   tag

How do you solve it?

use github action manual trigger to package rc version.

Special notes for your reviewer, ex. impact of this fix, design document, etc:

Checklist:

Tests:

• Unit test(positive and negative cases)
• Function test
• Performance test
• N/A

Affects:

• Documentation affected (Please add the label if documentation needs to be modified.)
• Incompatibility (If it breaks the compatibility, please describe it and add the label.）
• If it's needed to cherry-pick (If cherry-pick to some branches is required, please label the destination version(s).)
• Performance impacted: Consumes more CPU/Memory

Release notes:

None

Please confirm whether to be reflected in release notes and how to describe:

ex. Fixed the bug .....
None

[Sophie-Xie]

Thanks!

And I have some questions, if I enter the version number, is it v3.0.2 or 3.0.2? And Is the name of github tag still v3.0.2?

[yixinglu]

Thanks!

And I have some questions, if I enter the version number, is it v3.0.2 or 3.0.2? And Is the name of github tag still v3.0.2?

Input version of the workflow is following format: 3.0.2, there's an example in this parameter description. The tag name should be same as before, such as: v3.0.2.