chore(lume): stop mutating the repository-wide GitHub Latest release

[f-trycua]

Problem

The Lume release workflow publishes normal component releases but also passes --make-latest to .github/scripts/github_release.py.

This repository contains independent release streams such as lume-v* and cua-driver-rs-v*. A repository-wide GitHub "Latest" pointer cannot accurately represent all of them. Making every Lume release globally latest is therefore misleading for users and unsafe for any generic consumer that assumes /releases/latest identifies its own component.

Lume does not need this pointer for its normal install path:

• libs/lume/scripts/install.sh prefers the exact LUME_BAKED_VERSION updated by Release Please.
• LUME_VERSION provides an explicit version override.
• The API fallback scans releases and filters lume-v* tags.

Proposed change

• Continue publishing Lume releases as normal non-prerelease releases.
• Stop passing --make-latest from .github/workflows/cd-swift-lume.yml.
• Keep installer resolution component-scoped and version-pinned.
• Audit and remove the unused LATEST_RELEASE_URL constant if it is no longer referenced.
• Update workflow comments or release documentation that imply the repository-wide Latest pointer is authoritative.

Acceptance criteria

• A Lume release is published with prerelease: false and make_latest: false.
• The release contains the expected notarized assets and metadata.
• The baked-version install path still resolves the exact lume-v* tag.
• The explicit LUME_VERSION override still works.
• The component-scoped fallback still selects the highest valid Lume version without relying on /releases/latest.
• Tests confirm that publishing Lume does not change the repository-wide GitHub Latest pointer.

Context

This is release hygiene for a monorepo with independent component tags. It is separate from changing how any component installer chooses versions.