ci: add releases.toml automation for compatibility tracking

[JoshuaBatty]

Add CI automation to track dependency versions for each release:

• Add update_releases.sh script that extracts sway, fuel-core, and fuels-rs versions from Cargo.lock and appends entries to releases.toml
• Add update-releases job to CI that runs after publish-crates and opens a PR with the updated releases.toml
• Update RELEASING.md to document the new compatibility tracking step

The script only records dependency versions that the specific crate actually uses - it checks the crate's own Cargo.toml rather than recording all versions from the workspace's Cargo.lock.

This implements the compatibility tracking section from the forc-tooling monorepo RFC. The releases.toml file serves as an append-only log that fuelup and fuel.nix can use to determine compatible toolchain versions.

Also bump forc-wallet to 0.16.2 to test the automation after merge.

[cursor]

PR Summary

Adds CI job and script to append dependency versions to releases.toml on release and open a PR; bumps forc-wallet to 0.16.2 to exercise the flow.

• CI:
  • Add update-releases job in .github/workflows/ci.yml to extract crate/version from tag, fetch releases.toml from main, run updater, and open a PR with changes.
• Scripts:
  • Add .github/workflows/scripts/update_releases.sh to read Cargo.lock for sway-core, fuel-core, and fuels, and append a [[releases]] entry (crate, version, date, dependency versions) to releases.toml.
• Docs:
  • Update RELEASING.md to document the compatibility tracking step and its purpose.
• Crate versioning:
  • Bump forc-wallet to 0.16.2 (Cargo.toml, CHANGELOG.md); update Cargo.lock.

^{Written by Cursor Bugbot for commit 7bee68e. This will update automatically on new commits. Configure here.}

[github-actions]

LCOV of commit 7bee68e during CI #22

Summary coverage rate:
  lines......: 32.6% (361 of 1108 lines)
  functions..: 32.5% (53 of 163 functions)
  branches...: 26.4% (19 of 72 branches)

Files changed coverage rate: n/a