[WIP] Update branch snapping workflow for new versioning scheme

[Copilot]

Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.

Original prompt

I need to update the branch snapping workflow to align with a new versioning scheme. Currently we incrememnt the minor version in version.json every time we snap from main -> prerelease. The new versioning scheme will be different. The minor version should be incremented for every main -> prerelease snap, but stable releases (release branch) should get the next tens version. For example if the prerelease version was 2.74, then when it is snapped to release the version should become 2.80.

I believe we can accomplish this with the following changes

1. Add a helper function (in /tasks) to determine the next release version given the current version in version.json.
2. If snapping from prerelease -> release, we should take the branch created by the merge from prerelease to release (generally merge/prerelease-to-release) and push an update to the version.json to switch to the stable version to that branch. This would be handled by a new gulp task using the helper function in 1).

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.