Move (Re)Provider logic to Content Routers

[guillaumemichel]

The Reprovide logic is usually specific to the Content Router(s) in use. Hence, a Provider interface should be exposed through go-libp2p-routing-helpers, and the reprovide logic should move away from this repo to the specific Content Routers (e.g DHT, IPNI).

See:

• Reprovide Sweep libp2p/go-libp2p-kad-dht#824
• Delegate Reprovide to Content Routing System libp2p/go-libp2p#2175

[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.

[guseggert]

Related to ipfs/kubo#9682 and ipfs/kubo#9482

[hacdias]

This repository is no longer maintained and has been copied over to Boxo. In an effort to avoid noise and crippling in the Boxo repo from the weight of issues of the past, we are closing most issues and PRs in this repo. Please feel free to open a new issue in Boxo (and reference this issue) if resolving this issue is still critical for unblocking or improving your usecase.

You can learn more in the FAQs for the Boxo repo copying/consolidation effort.