build: extend release process with point releases

[yurii-vasyliev]

This pull request introduces support for "point" branches, enabling the creation and deployment of pinned beta releases based on specific commits and cherry-picked fixes. The changes update the release workflow, versioning logic, and documentation to clarify how and when to use these point releases.

Release workflow and branching strategy updates:

• The .github/workflows/release-and-build.yml workflow now triggers on pushes to point/** branches and treats them as beta releases, deploying to the ppa-build target. [1] [2]
• The scripts/calculate-version.cjs script is updated to generate beta version numbers for point/ branches, matching the format used for main.

Documentation improvements:

• RELEASES.md now documents the new point/YYYY-MM-DD branch type, its purpose, and how it fits into the overall branching strategy.
• A detailed example workflow ("Example C: Shipping a Pinned Beta") is added to RELEASES.md, explaining how to create, use, and retire point branches for targeted beta releases.## Summary

Summarize the changes made in this pull request. Include any relevant context or background information that would help reviewers understand the purpose and scope of the changes.

Release Impact

According to the [Landscape Server Release Cycle
This pull request introduces support for "point" branches, which enable the creation of pinned beta releases based on specific commits and cherry-picked fixes. The changes update the branching strategy documentation, CI workflow, and version calculation logic to recognize and handle point/YYYY-MM-DD branches as beta releases. This allows for more flexible and controlled beta releases without disrupting ongoing development on main.

Branching and Release Process Updates:

• Updated the documented branching strategy in RELEASES.md to include point/YYYY-MM-DD as a new branch type for pinned beta releases, clarifying its purpose and deployment target.
• Added a detailed example workflow in RELEASES.md for creating and managing point releases, including branch creation, cherry-picking, and cleanup instructions.

CI/CD and Versioning Enhancements:

• Modified the GitHub Actions workflow in .github/workflows/release-and-build.yml to trigger on pushes to point/** branches, ensuring CI builds are run for point releases.
• Updated the build destination logic in the workflow so that builds from main or any point/** branch are deployed to the ppa-build beta channel.
• Adjusted the version calculation script (scripts/calculate-version.cjs) to treat point/ branches like main, assigning them a beta version suffix.](https://docs.google.com/document/d/1sKAp5IvArpfArhMNojFwKOHm9LEdHKB4Et6tu1_-0GY/edit?tab=t.0), this change will target the following release cycle:

• Target Branch: dev / main (Beta)
• Version Impact:
  • Patch (Fix)
  • Minor (Feature)
  • Major (Breaking)

Checklist

• Changeset Added: I have run pnpm changeset and committed the resulting .md file.
• UI Verified: I have verified the changes locally.
• Linting: No linting errors are present (especially in scripts/).

Versioning Reminder

Important

This repository now uses CalVer ($YY.0M.Point.Patch$).
Please ensure your changeset description is clear, as it will be automatically added to the CHANGELOG.md upon merging to main.