ci: implement semantic release process

[andrewb1269hg]

Description:
The purpose of this PR is to create two workflows:

increment-next-main-release.yaml will increment the version.txt file to the next minor release (Ex: 0.58.x --> 0.59.0). This will be used when a release is complete and we are working on a new release version.

flow-trigger-release.yaml will apply a version tag using the git-semver tool with appropriate semantic release versioning, trigger our workflows for a release, and generate the release notes in a markdown format.

Related issue(s):

Fixes #14967

Notes for reviewer:

Checklist

• Documented (Code comments, README, etc.) - Roger has created documentation about the process we're transitioning to for release process of 0.59 and onwards.
• Tested (unit, integration, etc.) - Extensively tested. The latest for action results can be found here for incrementing the minor version number. The latest action results can be found here for triggering the official release process.

[andrewb1269hg]

Holding on merge until Nathan reviews this PR.

[andrewb1269hg]

@nathanklick I have resolved all comments on this PR and the changes are ready for verification.

I need to run appropriate checks to confirm everything functions as expected with this final version. I will have documentation available here of my full testing process before merging.

@rbarkerSL for awareness ^ please reapprove when you get a chance.

[andrewb1269hg]

Potential issue identified here:
I applied v0.59.98 at build-00058 tag. I then made a new branch, added a small commit, then applied v0.59.99. This simulates another publish on the release branch. See the attached picture to see what the branching structure looks like when the steps fail.

The semantic release script was then run on the mainline and silently failed. See the linked job here.