Refactor of dev prerelease auto-update-version workflow

[rashidnhm]

Context: Changes to the update_dev_version.yml

Description of the Change:
This PR introduces the following changes to the update_dev_version.yml workflow:

• Refactor dev_version_script.py to use python-semver
  • Why? -> It is generally more robust to parse and bump versions. In the previous version, it was assumed that the version on the PR was the same as master, then the pr version got bumped by 1. Though that is true for 99% of the cases, it left out a chance for a bad version to get by. The check is a bit more strict now, where the version is taken from master, bumped up by 1, then checked against the pr version.

Example of this in action:

• Create a branch off of master
• As of writing, the version in master is 0.36.0-dev29
• In your branch, update the version manually to 0.36.0-dev25 (Simulates someone accidentally drifting away from the master version by more than 1)

With the previous version of the workflow, the pr would get auto updated to: 0.36.0-dev26. This is technically invalid as that version already exists. Though it can be caught during manual PR review it might get by as well.

With the new workflow, the pr would get auto updated to: 0.36.0-dev30.

• Change update_dev_version.yml to run on pull_request_target
  • Why? -> This would let the action trigger from the master branch instead of the PR branch, which means it will have access to secrets (even if the PR is from a fork!) and would be able to push to PRs as ringo bot. Usage of the token also means that when a new commit is pushed, new CI will be kicked off.

Other notable changes:

• The commit pushed by the bot now includes the version it bumped from/to.
  
  

Benefits:
Noted in the section above.

Possible Drawbacks:
With CI triggering itself, there is always a possibility CI recursively calling itself infinitely. The base case here is if the version matches what is expected, then nothing is pushed to the PR.

Related GitHub Issues:
None. sc-61382

[github-actions]

Hello. You may have forgotten to update the changelog!
Please edit .github/CHANGELOG.md with:

• A one-to-two sentence description of the change. You may include a small working example for new features.
• A link back to this PR.
• Your name (or GitHub username) in the contributors section.

[mlxd]

Thanks @rashidnhm
Just a few quick questions

[maliasadi]

Nice work! 🥳

[mlxd]

Thanks @rashidnhm
No further issues from my end

[maliasadi]

Thanks @rashidnhm 💯