Change pre-release.yml for multi-platform builds

[TheGupta2012]

Summary of changes

• Added platform specific builds in pre-release.yaml
• Updated the pre_build.sh script to detect whether we are in pre-release, if yes, then change the version of the toml file to dev version.
• Updated the CIBW_BEFORE_BUILD command to include the project name as an argument.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

📢 Thoughts on this report? Let us know!

[ryanhill1]

With these updates, we no longer need the create_dev_build.sh script, right?

[TheGupta2012]

Yea, idts that the script would be needed.

The only thing which is unclear to me is how the pre-release version numbers would be tracked. For instance, say we have published v0.1.0-a1. Once we trigger the pre-release flow, how will it know that the next version to be published is v0.1.0-a2 if the toml version stays at v0.1.0-alpha?

[ryanhill1]

@TheGupta2012 It does so using qbraid_core.system.versions.get_latest_package_version() with the option prerelease=True. This function makes a GET request to PyPI, and gets back a list of all of the releases for the given package, and is used as a helper within qbraid_core.system.versions.get_prerelease_version(). And then if the pyproject.toml version ends in -alpha, we get that latest "alpha" release matching that version and bump it by one. Same thing for "beta" and "rc". Or if no pre-releases for that marker exist yet, we set it to 0.

[TheGupta2012]

@ryanhill1 have also added the change for sdist version bump