feat(ci): include Linux CLI and Relay artifacts in beta releases

[wgqqqqq]

Summary

Beta Desktop Package runs currently skip Linux CLI/Relay archives and the Relay container image. Include both Linux architectures and the multi-platform image in Beta releases, and require all producers to succeed before publishing the Release.

Type and Areas

Feature / CI — Desktop release workflow, Linux CLI/Relay packaging, release documentation.

Motivation / Impact

• Publish Linux x86_64/aarch64 CLI and Relay archives with checksums and signatures, linux-binaries.json, and the signed relay-image.json descriptor on the versioned Beta release.
• Publish Relay images with explicit Beta version tags only; retain stable ownership of the latest image tag and default install/update/deploy entry points.
• Use the current repository and owner for release URLs and image publication, including forks.
• Share asset staging and verification between stable and Beta. Artifact-only runs build archives and validate images without pushing them; explicit image-only backfills remain publishing operations.

Verification

• pnpm run check:repo-hygiene: passed, including the product identity audit; test repositories use the canonical OpenBitFun name.

• pnpm run check:github-config: 24 passed, 1 skipped because PowerShell is unavailable locally.

• node --test scripts/relay/package-contract.test.mjs scripts/tauri-release-manifest.test.mjs: 12 passed.

• git diff --check: passed.

• Regression coverage exercises actual workflow conditions across producer results, stable/Beta image tag selection and backfills, versioned Beta manifest URLs/signatures, and fixture asset staging.

Reviewer Notes

No packaging or release workflow was manually dispatched, as requested; actual platform builds, image pushes, and deployment smoke tests are deferred to the later packaging run. Tests use fixtures, not built binaries. No remote runtime scenario was exercised. Beta Relay deployment remains manual by explicit image tag/digest; the existing one-click stable deployment path is unchanged. GHCR publication requires package permissions and public anonymous pull access.

Checklist

• This PR is focused and does not include secrets, temporary prompts, generated scratch files, or unrelated artifacts.
• Relevant verification is recorded above, or skipped checks are explained.
• User-facing strings, docs, and locales are updated where applicable.