fix: rename forc-wallet targets from Rust triples to simplified names

[JoshuaBatty]

Summary

• Updates all channel TOML files to use simplified target naming for forc-wallet
• Renames section headers and URL filenames from Rust triples to simplified format:
  • aarch64-unknown-linux-gnu → linux_arm64
  • x86_64-unknown-linux-gnu → linux_amd64
  • aarch64-apple-darwin → darwin_arm64
  • x86_64-apple-darwin → darwin_amd64
• 1137 files updated with 4943 insertions/deletions

Notes

• fuel-core and fuel-core-keygen entries are intentionally unchanged (their release assets have not been renamed)
• Nightly URLs from sway-nightly-binaries retain old naming in URLs since those assets haven't been renamed in that repo Update: Nightly assets now use simplified naming after feat: use simplified target names for forc-wallet and forc-crypto releases sway-nightly-binaries#80 was merged

Validation

• Verified renamed asset URLs exist and return HTTP 200
• All TOML files pass syntax validation
• Confirmed no old naming remains in forc-wallet sections

Closes #809
Related: #808
RFC: FuelLabs/sway-rfcs#49

[cursor]

PR Summary

Renames forc-wallet target keys in channel TOMLs from Rust triples to simplified platform names (darwin/linux arm64/amd64) across channels, leaving URLs and other packages unchanged.

• Channels/TOML:
  • Rename forc-wallet target section headers from Rust triples to simplified platform names:
    • aarch64-apple-darwin → darwin_arm64
    • x86_64-apple-darwin → darwin_amd64
    • aarch64-unknown-linux-gnu → linux_arm64
    • x86_64-unknown-linux-gnu → linux_amd64
  • Apply across nightly channel files (and other channel TOMLs) without altering referenced assets; URLs remain as originally published.
  • No changes to fuel-core/other packages beyond forc-wallet target key renames.

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

[kayagokalp]

Will this break existing fuelup parsing logic? I remember we have things like

fuelup/src/target_triple.rs

Line 35 in 40b4239

pub fn from_host() -> Result<Self> {

but can't exactly remember if these target triple constructs are actually matched against these toml files we are modifying in this PR.

Even if it is going to break things we can merge it and fix fuelup parsing logic afterwards. As it is hard to assess if things will go down or not without actually making the change to the toml files being consumed

[JoshuaBatty]

That's a great point, i'm going to look into that tomorrow and make sure this is handled correctly. Cheers!

[JoshuaBatty]

Will this break existing fuelup parsing logic? I remember we have things like

fuelup/src/target_triple.rs

Line 35 in 40b4239

pub fn from_host() -> Result<Self> {

but can't exactly remember if these target triple constructs are actually matched against these toml files we are modifying in this PR.
Even if it is going to break things we can merge it and fix fuelup parsing logic afterwards. As it is hard to assess if things will go down or not without actually making the change to the toml files being consumed

This is addressed now in this commit 1535007

thanks for pointing it out!