add workflow to build and release wheel

[celestialli]

What this PR does / why we need it?

This is a continuing work of #716.
This PR add workflow to build and release wheel, and also release source to PYPI.
We have 3 conditions to trigger the workflow:

1. PR to main and *-dev
2. push to main and *-dev
3. push tag with name of v*

Release to PYPI will only be done under condition 3. Under condition 1 and 2, it will generate .tar.gz and build .whl, upload to github artifacts but will not release.

update:
Will build .whl and upload to github artifacts with scheduled task.

Does this PR introduce any user-facing change?

No.

How was this patch tested?

All triggered conditions are well tested with my fork repo.

[wangxiyuan]

have you test the twine upload step? I notice that the name of the wheel package is not correct for pep guide. for example, it's vllm_ascend-0.1.dev1+g6a4fc33-cp310-cp310-linux_aarch64.whl. but for pep guide, it should be something like vllm_ascend-0.1.dev1+g6a4fc33-cp310-cp310-manylinux2014_aarch64.whl

https://packaging.python.org/en/latest/specifications/platform-compatibility-tags/#platform-tag

[celestialli]

have you test the twine upload step? I notice that the name of the wheel package is not correct for pep guide. for example, it's vllm_ascend-0.1.dev1+g6a4fc33-cp310-cp310-linux_aarch64.whl. but for pep guide, it should be something like vllm_ascend-0.1.dev1+g6a4fc33-cp310-cp310-manylinux2014_aarch64.whl

https://packaging.python.org/en/latest/specifications/platform-compatibility-tags/#platform-tag

Well, I have tested with the twine upload but a error happened, mostly because lack of a project on my PYPI account. It is expected to run smoothly if we get the right PYPI_TOKEN and we have the right project on the account, please don't worry.
manylinux tag is there because it is compiled under manylinux image, but as I see, it is not mandatory norms. We can see,
whl filename of sglang is named with sglang-0.4.6.post3-py3-none-any.whl.
https://pypi.org/project/sglang/#files

[wangxiyuan]

you can reigster a pypi account and try twine upload with a test package local. it's quite easy

[celestialli]

have you test the twine upload step? I notice that the name of the wheel package is not correct for pep guide. for example, it's vllm_ascend-0.1.dev1+g6a4fc33-cp310-cp310-linux_aarch64.whl. but for pep guide, it should be something like vllm_ascend-0.1.dev1+g6a4fc33-cp310-cp310-manylinux2014_aarch64.whl

https://packaging.python.org/en/latest/specifications/platform-compatibility-tags/#platform-tag

linux_aarch64 suffix will indeed invoke a twine error. It's fixed, thanks. And I have added a scheduled task to build a .whl every day.

[Yikun]

Thanks for contributions, I will take a look before merge.

[Yikun]

Just a rename