Problem: upgrading to Kubo 0.23.0 seems to cause issues when syncing a new node

[odesenfans]

The sync of a new test node stopped because Kubo seemed too busy updating its own DHT. This warning pops in the logs:

🔔🔔🔔 YOU ARE FALLING BEHIND DHT REPROVIDES! 🔔🔔🔔

⚠️ Your system is struggling to keep up with DHT reprovides!
This means your content could partially or completely inaccessible on the network.
We observed that you recently provided 148 keys at an average rate of 9.182511883s per key.

💾 Your total CID count is ~97730 which would total at 249h16m46.88632559s reprovide process.

⏰ The total provide time needs to stay under your reprovide interval (22h0m0s) to prevent falling behind!

💡 Consider enabling the Accelerated DHT to enhance your reprovide throughput. See:
https://github.com/ipfs/kubo/blob/master/docs/config.md#routingaccelerateddhtclient

The tx and message processor tasks were failing to fetch data from IPFS as well, blocking the pipelines.

We reverted to 0.15.0 for now but this needs to be investigated for a future release.