feat(p2p/discovery)!: Implement archival discovery + syncing of historic blocks and blobs

[renaynay]

This PR introduces the discovery of nodes advertising on the archival topic for the purpose of being able to request blobs and blocks that are older than the sampling window.

In order to do so, there are now 2 instances of discovery (one for full nodes -- all nodes running full block sync within the sampling window, and one for archival nodes -- nodes that sync, store and serve all historic data) and 2 instances of peer managers (one for full and one for archival).

This PR is breaking due to changes to metrics names.

Please also note that this PR introduces the ability to perform archival sync of blobs + blocks for LIGHT AND FULL nodes only regardless of whether the full nodes have pruning enabled or not. Bridge nodes that have previously had pruning enabled will NOT be able to request historic data from the consensus core node. The bridge node must run in archival mode (without --experimental-pruning enabled) in order to access historic data.

Bridge and Full nodes in archival mode (without --experimental-pruning)

2024-05-10T15:21:44.490+0200	INFO	share/discovery	discovery/manager.go:30	starting discovery	{"topic": "full"}
2024-05-10T15:21:44.491+0200	INFO	share/discovery	discovery/manager.go:33	advertising to topic	{"topic": "full"}
2024-05-10T15:21:44.491+0200	INFO	share/discovery	discovery/manager.go:30	starting discovery	{"topic": "archival"}
2024-05-10T15:21:44.491+0200	INFO	share/discovery	discovery/manager.go:33	advertising to topic	{"topic": "archival"}

Bridge and Full nodes running --experimental-pruning

2024-05-10T15:19:20.698+0200	INFO	share/discovery	discovery/manager.go:30	starting discovery	{"topic": "full"}
2024-05-10T15:19:20.698+0200	INFO	share/discovery	discovery/manager.go:33	advertising to topic	{"topic": "full"}
2024-05-10T15:19:20.698+0200	INFO	share/discovery	discovery/manager.go:30	starting discovery	{"topic": "archival"}

Light nodes

2024-05-10T15:20:42.440+0200	INFO	share/discovery	discovery/manager.go:30	starting discovery	{"topic": "full"}
2024-05-10T15:20:42.440+0200	INFO	share/discovery	discovery/manager.go:30	starting discovery	{"topic": "archival"}

---

TODO

• test archival request routing per node type
• renaming some things inside discovery away from being full-node-centric
• rebase
• swamp test

For follow-up PR:

• clarify / make disc metrics generic as there will now be 2 instances of discovery happening

Nice to have;

• benchmarks for LN

[walldiss]

Can't tell if nodebuilder is correct. Changes are quite complex and difficult to fully understand. So relying on tests for correctness. Not a good thing, so we should prioritise refactoring of share module construction.

[Wondertan]

There are two main comments. The introduced Manager is net negative and the need for EnableAdvertise in config is unclear.

[Wondertan]

I want to ship pruning and unblock this PR, so approving,
Under different circumstances, I would request a redesign.
This PR leaves too much dech debt behind it

[walldiss]

Great effort on the nodebuilder in this PR! However, it's still pretty tough to tell if everything's correct. My biggest concern is that the feature needs thorough testing to ensure all setups work as intended. Given its complexity, future changes might get tricky, so let's prioritize refactoring as soon as we have the resources.