Bootstrapping seeds are refreshed during bootstrap

### Describe the problem you discovered

When a new node join the network it retrieve the bootstrapping nodes from the network, then it start the bootstrap self repair. But the bootstrapping nodes are refreshed during the self repair and the first summary repaired only contains only one node, so the bootstrapping nodes are refreshed with this single node.
If the bootstrap failed and restart the node only have this single node as bootstrapping nodes and if this node is not available anymore the bootstrap while fail in loops

### Describe the solution you'd like

Bootstrapping seeds should always be refreshed with the last data availables, not from the nodes of old summaries

### Epic

_No response_

Trace the bootstrap self-repair flow and the point where bootstrapping seeds are refreshed; the issue names no files or tests. Verify how the latest available data is selected versus nodes from older summaries, and consider the work done when a restart retains the latest usable seed set instead of a single stale node.

Written by the indexing model from the issue text.