Consider basing fuelup's component fetching on IPFS? Or providing an IPFS backup?

Currently, `fuelup` fetches all binaries directly from GitHub. This means if GitHub goes down for whatever reason, `fuelup` may fail to fetch tools during installation / updating.

Perhaps we should consider fetching via IPFS?

This might involve:

1. Setting up a Fuel Labs IPFS node.
2. Having the IPFS node automatically fetch all fuel repo binaries as they're published and host them.
3. Host a "CID index", i.e. a mapping of tool versions to their associated CIDs (IPFS hashes) either on GitHub (similar to our channels) or the IPFS node.
4. At fuelup's compile time, we bake in a table of all known tool versions and their CIDs. This way, if our CID index goes down, we can at least attempt to fetch these versions that were known at compile time via IPFS.
5. During fuelup installation, updating or checking for new packages, fuelup maintains a local CID index (e.g. something simple like a directory with file for each binary version containing its hash). We can fallback to this local table in the case that our CID index goes down.