Add semver ordering guidance to release skills

[mattleibow]

Prevents selecting the wrong release branch when both preview and stable branches exist (e.g., picking 3.119.2-preview.3 instead of 3.119.2).

In semver, bare versions are always newer than prerelease variants: 3.119.2 > 3.119.2-preview.3.

Changes

• release-testing: Added critical section before Step 1 with step-by-step process to find the correct branch
• release-branch: Added semver check in auto-detect and ordering warning in Step 2
• release-publish: Added semver ordering subsection in Step 1

[github-actions]

Triage Summary

No labels will be applied as the issue does not relate to any specific operating system, platform, or backend technology.

This issue is not a regression and does not indicate any compatibility or performance concerns.

Additional remarks:

• The issue relates to improvements in release branch management linked to semantic versioning, but lacks the necessary context to assign relevant labels such as documentation or build areas.

Detailed Summary and Actions

Summary of the triage:

• No specific platform or operating system labels can be assigned as the issue does not mention any.
• The issue does not point to any compatibility, performance, or reliability problems, and therefore does not warrant a regression label.
• There are no backend technology or rendering framework references in the issue content for meaningful label application.
• The main focus of the issue is on release branch management improvements related to semver, but does not link directly to existing documentation labels.

Summary of the actions that will be performed:

Action	Item	Description
No Action	N/A	No labels can be applied as the issue lacks necessary details and context.

This entire triage process was automated by AI and mistakes may have been made. Please let us know so we can continue to improve.