Issue Addressed

Part of

• Improve range sync with PeerDAS #6258

To address PeerDAS sync issues we need to make individual by_range requests within a batch retriable. We should adopt the same pattern for lookup sync where each request (block/blobs/columns) is tracked individually within a "meta" request that group them all and handles retry logic.

Proposed Changes

• Building on Generalize sync ActiveRequests #6398

second step is to add individual request accumulators for blocks_by_range, blobs_by_range, and data_columns_by_range. This will allow each request to progress independently and be retried separately.

Most of the logic is just piping, excuse the large diff. This PR does not change the logic of how requests are handled or retried. This will be done in a future PR changing the logic of RangeBlockComponentsRequest.

Before

• Sync manager receives block with SyncRequestId::RangeBlockAndBlobs
• Insert block into SyncNetworkContext::range_block_components_requests
• (If received stream terminators of all requests)
  • Return Vec<RpcBlock>, and insert into range_sync

Now

• Sync manager receives block with SyncRequestId::RangeBlockAndBlobs
• Insert block into SyncNetworkContext:: blocks_by_range_requests
• (If received stream terminator of this request)
  • Return Vec<SignedBlock>, and insert into SyncNetworkContext::components_by_range_requests
  • (If received a result for all requests)
    • Return Vec<RpcBlock>, and insert into range_sync