Improve UX when could not get latest version of migration

[fatasy1]

Initializing daemon...
go-ipfs version: 0.12.2
Repo version: 12
System version: amd64/windows
Golang version: go1.16.15
Found outdated fs-repo, migrations need to be run.
Looking for suitable migration binaries.
Need 1 migrations, downloading.
Downloading migration: fs-repo-11-to-12...
Fetching with HTTP: "https://ipfs.io/ipfs/QmdaCHYBDHEhXCMoynH5UcohEay6m1XayZCcxWZzKAHNVN/fs-repo-11-to-12/versions"
Fetching with HTTP: "https://ipfs.io/ipfs/QmdaCHYBDHEhXCMoynH5UcohEay6m1XayZCcxWZzKAHNVN/fs-repo-11-to-12/versions"
Fetching with HTTP: "https://ipfs.io/ipfs/QmdaCHYBDHEhXCMoynH5UcohEay6m1XayZCcxWZzKAHNVN/fs-repo-11-to-12/versions"
Error fetching: exceeded number of retries. last error was http.DefaultClient.Do error: Get "https://ipfs.io/ipfs/QmdaCHYBDHEhXCMoynH5UcohEay6m1XayZCcxWZzKAHNVN/fs-repo-11-to-12/versions": dial tcp 108.160.170.45:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Fetching with IPFS: "fs-repo-11-to-12/versions"
Error fetching: context deadline exceeded
could not get latest version of migration fs-repo-11-to-12: 2 errors occurred:
	* exceeded number of retries. last error was http.DefaultClient.Do error: Get "https://ipfs.io/ipfs/QmdaCHYBDHEhXCMoynH5UcohEay6m1XayZCcxWZzKAHNVN/fs-repo-11-to-12/versions": dial tcp 108.160.170.45:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
	* context deadline exceeded

Failed to download migrations.
The migrations of fs-repo failed:
  failed to download migrations: fs-repo-11-to-12
If you think this is a bug, please file an issue and include this whole log output.
  https://github.com/ipfs/fs-repo-migrations
migration peer 12D3KooWNu3nnfeqRUjf3avM8axKrFsDjoFuUhwbgk5q9gHqT7Dz shutdown

Error: failed to download migrations: fs-repo-11-to-12
```

[welcome]

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

• "Priority" labels will show how urgent this is for the team.
• "Status" labels will show if this is ready to be worked on, blocked, or in progress.
• "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

[SgtPooki]

@lidel to provide further information, but go-ipfs should provide a more meaningful error than 'context deadline exceeded'

[lidel]

When download fails, user gets error:

Failed to download migrations.
The migrations of fs-repo failed:
  failed to download migrations: fs-repo-11-to-12
If you think this is a bug, please file an issue and include this whole log output.
  https://github.com/ipfs/fs-repo-migrations

There are various ways we could improve UX here:

1. Make HTTP transport more robust by using fallback gateways on different domains – we track that in Switch migration fetcher to CAR #8851 already.
   • The Biggest one, because it could even try gateways from https://ipfs.github.io/public-gateway-checker/ (after go-ipfs 0.13 with feat(gateway): Block and CAR response formats #8758 ships and gateways update)
2. Make bitswap (IPFS) transport more robust by having bootstrappers from different organizations, geographical regions and AS.
   • Sadly, this won't help if non-HTTPS traffic is blocked
3. Improve error
   • A better, actionable error would go long way. We should have connectivity test tools in ipfs diag --help commands, and the error should have example comands that user can run to diagnose the source of connectivity errors.

If someone wants to work on (3) – help wanted.

[jvoisin]

This is what I'm getting on Alpine Linux :

~ # cat /var/log/ipfs/ipfs.log 
Initializing daemon...
Kubo version: 0.21.0
Repo version: 14
System version: amd64/linux
Golang version: go1.20.7
Found outdated fs-repo, migrations need to be run.
Looking for suitable migration binaries.
Need 1 migrations, downloading.
Failed to download migrations.
The migrations of fs-repo failed:
  linux-musl not supported, you must build the binary from source for your platform
If you think this is a bug, please file an issue and include this whole log output.
  https://github.com/ipfs/fs-repo-migrations

Error: linux-musl not supported, you must build the binary from source for your platform
~ #

sparking a couple of questions:

• "Found outdated fs-repo, migrations need to be run." : what does it mean? A link to the relevant documentation should be provide. Also, how outdated? what version is it, and what version is needed?
• "Looking for suitable migration binaries." what is the name of the binary kubo is looking for?
• "Need 1 migrations, downloading.": why is kubo trying to download binaries from the internet to execute them!?