Request for a feature in CLI: Combining automatic content routing based discovery and --providers value.

[agmap]

Sometimes the automatic content routing based discovery finds no providers/candidates.
So I have to add manually additional --providers value which are not on DHT or cid.contact.
Unfortunately, this disables automatic content routing based discovery.

It would be very helpful if I could define via CLI when adding one or more –providers value that the that the automatic content routing based discovery remains activated.

The definition of the discovery sequence would also be very helpful:

1. first automatic discovery and then --provider
   or
2. first --provider and then automatic discovery

I would like to add this function, but unfortunately I am not able to do so.

Or at least add the http trustless gateway --provider http://trustless-gateway.link --provider http://ipfs.io into the default automatic content routing based discovery. 🙏 @rvagg @willscott

[m0ar]

Chiming in randomly here: this would be hugely helpful when trying to fish out large collections of CIDs, where most resolve quickly in gateways but some are only retrievable directly from super sluggish peers. Being able to prefer a given trustless gateway, and falling back to automatic routing would save soo much time 🙏

[agmap]

@willscott @rvagg Can you please look into this request. I realy need it.
Add at least one flag in the CLI to include the providers in the automatic discovery instead of disabling the automatic discovery.
This way I can add trustless-gateway.link into the providers value and lassie fetch using cid.contact and delegated-ipfs.dev/routing.
Also related to #489