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.
• Test Procedure Documentation captured here in Notion

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
✅ +0.16% (target: -1.00%)	✅ ∅

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (ad099ae)	96992	70495	72.68%
Head commit (da0afa9)	97741 (+749)	71194 (+699)	72.84% (+0.16%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#17440)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

_{Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more}

[andrewb1269hg]

Created Issue #17955 to capture the alpha tag creation.

[andrewb1269hg]

Increment Next Main Release workflow tested and successful here:
https://github.com/hiero-ledger/hiero-consensus-node/actions/runs/13511623973/job/37752812819

[andrewb1269hg]

Testing the standard release process here was successful:
https://github.com/hiero-ledger/hiero-consensus-node/actions/runs/13511799402
Applied v0.98.99 to build-00058
Workflow applied v0.99.0 to build-00059 correctly

[andrewb1269hg]

Testing with alpha tags. Alpha tags do not interfere with the official release numbers:
https://github.com/hiero-ledger/hiero-consensus-node/actions/runs/13511867439/job/37753478975

Manually applied:
v0.97.99 applied to build-00057
v0.98.99-alpha.0 applied to build-00058

Workflow applied:
v0.98.0 applied to build-00059 which ignored the previously cut alpha release

[rbarker-dev]

lgtm