Support specify release candidate number in x.py package source

[tisonkun]

Search before asking

• I had searched in the issues and found no similar issues.

Motivation

Otherwise, the RC always has the same tag name as the formal release name. And it's awkward to force-push for overwriting refs.

Solution

cc @PragmaTwice @git-hulk may you check where we should use -rcX during the release process?

Are you willing to submit a PR?

• I'm willing to submit a PR!

[PragmaTwice]

Sure, we can make it push to a tag with rc suffix.

[tisonkun]

@PragmaTwice what I'm afraid of is that there is still other place we need rc suffix except the git tag :D

[ZENOTME]

I can help with this.

Not sure whether my understand is correct, it's to support
./x.py package source -v 2.3.2 -rc 1 and then create a tag '2.3.2-rc1'.

[tisonkun]

@ZENOTME Thanks for your input! That sounds good to me. Please go ahead.