[feat:] added support for cargo-binstall

[SkySingh04]

This PR updates the CI workflow to:

1. Consistent Naming Convention: Standardizes the naming of artifacts produced during the build process across different operating systems and architectures. This new naming convention adheres to the format:

   • For Windows:
     • fnm-x86_64-pc-windows-msvc.zip
     • fnm-arm64-pc-windows-msvc.zip
   • For macOS:
     • fnm-aarch64-apple-darwin.zip
     • fnm-x86_64-apple-darwin.zip
   • For Linux:
     • fnm-x86_64-unknown-linux-musl.zip
     • fnm-arm64-unknown-linux-gnueabihf.zip

2. Added binstall.toml file to support cargo binstall fnm

Note : Currently the binstall.toml file is set to target packages in existing release nomenclature like https://github.com/Schniz/fnm/releases/download/v1.37.2/fnm-macos.zip

Related Issue : #1280

[changeset-bot]

⚠️ No Changeset found

Latest commit: 238160e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
fnm	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 13, 2024 8:53pm

[Schniz]

oh no, is there a way it'll be automatic
i might need to append this portion upon release?

[Schniz]

that's an exciting change
but can we make this nonbreaking for the current installation script by uploading artifacts with both the new and old name? i don't mind having duplicated files with different names just to maintain backward compatibility :)