chore(release): rong_crypto 0.6.0 and 0.6.1 patches

[butterflyfish]

Summary

Release only the packages that changed since their last publish. Selection follows the master release-plan job (publish.sh --changed --dry-run) plus adding rong_crypto to the publish crate lists (it was missing, so that plan could not include it).

• rong_crypto 0.6.0 — first publish; Web Crypto subset on globalThis.crypto
• rong_core 0.6.1 — TaskScope / begin_task_scope
• rong_abort 0.6.1 — dropped signal parks receivers instead of spinning
• rong_http 0.6.1 — fetch abort-bridge ends when the transport is done
• rong_modules 0.6.1 — optional crypto feature (also in all)
• rong_typegen 0.6.1 — Crypto ambient types in the logic-web profile
• @rongjs/rong 0.6.1 — crypto subset and Storage.has types

No workspace-wide bump. Engines, rong, rong_rt / rong_command / rong_storage (already 0.6.1), @rongjs/rong-skill, and @rongjs/test stay put. Cargo ^0.6.0 accepts these 0.6.1 crates. rong_crypto stays at 0.6.0 for its first crates.io version.

Validation

• Relied on GitHub Actions host CI for platform coverage
• GitHub Actions CI passed

Master CI at https://github.com/LingXia-Dev/Rong/actions/runs/34591747589 already passed for this source (crypto + abort + task-scope). This PR is version/changelog/script-list only; host CI on the PR is the remaining gate.

Release Impact

• CHANGELOG.md updated
• Version bump included

After merge, run Publish Packages from master:

• package_scope=all
• rust_selection=--changed
• package_tags=always
• product_release empty (crate/npm tags only, no v0.6.2 product tag)

rong_crypto is a first publish, so crates.io Trusted Publishing is not attached yet; the workflow's CARGO_REGISTRY_TOKEN fallback is required for that crate. Configure the trusted publisher after the first upload.