Redesign the GitHub Actions CI workflow to make it clearer and more reliable

[pzhlkj6612]

I found that our CI scripts (test-install-qt.yml and upload-release-artifacts.yml) will not create a continuous release when a push event occurs. The continuous release is only triggered when another release is created.

After re-reading all the scripts, I think we may need to re-design them. My expected workflow is as follows and this workflow should work with continuous build, prerelease and release:

1. Check the code (style, quality, etc.).
2. Build and test:
   • Build and test the Python package.
   • Build and test the standalone exe on Windows.
3. If everything goes well, create a release, upload the standalone exe to this release, and upload the Python package to PyPI or Test PyPI (I think uploading the ".wheel" file to the release also makes some sense).

To implement the above workflow, we may need to use workflow_run in our scripts.

Please set the milestone of this issue to "future"; we need the version 2.0.0.

[pzhlkj6612]

New objective: append the version number to the filename of the asset in non-continuous releases.

from: #404 (comment)

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days