feat: rework release flow and fix build

[Gr1dlock]

Summary

Adopt bedrock-style release workflow with automated version bumping and unified releases across all platforms (Swift, Kotlin, JS).

Changes

New Release Workflow

• Add initiate-release.yml - manually triggered workflow that bumps version across all platforms and creates a release PR
• Single source of truth: version now lives in Cargo.toml and syncs to Swift, Kotlin, and JS automatically

Improved Publish Workflows

• Add pre-release version checks to prevent duplicate releases (Swift, Kotlin, JS)
• Swift: Use new archive-swift.sh script for cleaner Package.swift generation
• Kotlin: Read version dynamically from Cargo.toml instead of hardcoding

Bug Fixes

• Fix cross installation by using stable release (v0.2.5) instead of git HEAD
• Fix Swift naming conflict in Request+Convenience.swift (string → stringValue)

How to Release (New Process)

1. Go to Actions → "Initiate Release" → Run workflow
2. Select bump type: patch, minor, or major
3. Review and merge the auto-created PR
4. All platforms publish automatically

[Takaros999]

@codex review

[chatgpt-codex-connector]

To use Codex here, create a Codex account and connect to github.

[paolodamico]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 642bc72d4c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Remove invalid top-level workflow key

GitHub Actions does not accept a top-level description field in workflow files (only keys like name, on, jobs, etc. are valid). This makes the workflow invalid and prevents it from being loaded or manually dispatched, so the new release flow can’t run at all until the key is removed or moved to a supported location.

Useful? React with 👍 / 👎.