Move Reprovider config to Provider

[guillaumemichel]

Checklist

• My issue is specific & actionable.
• I am not suggesting a protocol enhancement.
• I have searched on the issue tracker for my issue.

Description

The same system is managing provides and reprovides. Having 2 distinct configs for it is confusing.

Besides, reproviding is a DHT specific behaviour, and may not apply to other providing systems. In a world where the DHT implementation works perfectly as expected, most users don't need to know that there is a reprovide operation.

The Reprovider config can be deprecated.

There are currently 2 parameters in the Reprovider config:

• Reprovider.Strategy -> Provider.Strategy
• Reprovider.Interval should be specific to each DHT with providing enabled, in a world where we use configurable routers/DHTs (see the composable routers should be powerfull enough to configure multi-dhts setups and we should drop the adhoc dht dual #10075). As a first step, we could move it to Provider.ReprovideInterval or Provider.DHT.ReprovideInterval.

Ideally, other provider/reprovider options that are specific to a routing system, should be configured as part of the routing system itself.

Related: #10886 (comment), #10834 (comment)

[lidel]

Assigning to myself, I'll do the repo and config migration as I also want to refine reusable utils for embedded migrations (and now we will have two).

Have prototype working, just need more testing. I'll open a PR against #10834 so its easier to review.