core/node: prioritize announcing pin roots

[hacdias]

This should close #10365.

• Rewrite the provider and reprovider tests in Go
• Depends on provider: prioritize roots and introduce NewPrioritizedProvider boxo#595

[aschmahmann]

and figure out how on earth I will test that

A couple options that seem reasonable:

1. Don't fully test end-to-end and just test the functions that get implemented for announcements
2. Test end-to-end but with a chunk of code running that processes delegated provides (not sure what the state of these is at the moment)

Both of these would let you capture ordering without being that annoying (e.g. you could also run a custom DHT server node instead of using a delegated router for provides).

[lidel]

Lgtm, but we need updates to internals from ipfs/boxo#595 to avoid memory usage when providing non-roots (the remainder of datatstore).

[lidel]

Tested with and without accelerated client, seems to work ok.
AFAIK we don't have any announcement benchmarks we could run, but eyeballing ipfs stats provide seems to be no slower than the old all.
I think doing this by default is net positive, but included flat strategy below as a precaution.