feat(ci): automate SNAPSHOT version updates in develop post-release

[shawnchan]

TODO

• restrict Tag Creation to GitHub Actions Only

Sensitive Credential Checks

• As the author of these changes, I have checked for any sensitive credentials prior to this review being requested.
• As a reviewer of these changes, I have checked for any sensitive credentials prior to approving this merge.

Motivation and Context

• Automatically updates the pom.xml version in the develop branch to the next -SNAPSHOT version after a release (e.g., 1.2.0 → 1.2.1-SNAPSHOT).
• Developers: No longer need to manually bump versions after releases.
• CI/CD: Ensures develop always reflects the next planned version.

Description

• Add GitHub Action to bump version to next SNAPSHOT post-release
• Trigger on new version tags (v*)
• Update POM version and push to develop branch

How Has This Been Tested?

• Manually tested by simulating a tag push:

  git tag v1.2.0-test && git push origin v1.2.0-test

• Verified:
• develop branch’s pom.xml updated to 1.2.1-SNAPSHOT.
• Commit is signed and tagged properly.

Screenshots (if appropriate):

Checklist:

• The base branch is set to develop
• It contains only changes required by issue (does not contain other PR)