fix: beaconBlocksMaybeBlobsByRoot() to handle single block root

[twoeths]

Motivation

• fix this mismatch error at synced time same to fix: peerDAS - fix mismatch error when downloading columns at synced time #7467

^[[39m: matchBlockWithDataColumns2 dataColumnIndexes=11 15, reque        stedColumnsPresent=false, slot=38584, peerClient=Lighthouse-cgc:128
2609158 Feb-12 18:58:44.857[sync]            ^[[34mdebug^[[39m: Missing or mismatching dataColumnSidecars from peerId=16U        iu2HAmJyaVGkRGR9ACqompkoge8T2x4KFH4KbzDkh7zz6uN2JX for blockSlot=38584 with numColumns=8 dataColumnSidecars=2 req        uestedColumnsPresent=false received dataColumnIndexes=11 15 requested=11 15 65 71 72 73 83 108 allBlocks=1, allDa        taColumnSidecars=2, peerId=16Uiu2HAmJyaVGkRGR9ACqompkoge8T2x4KFH4KbzDkh7zz6uN2JX, nodeId=0x70a752f736fd0254c715ae        31a3b64d9f3e011c1ca38e7f828d6d7f7bdf4391aa, blobKzgCommitmentsLen=6, peerClient=Lighthouse-cgc:128

• this is the logic inside beaconBlocksMaybeBlobsByRoot()

Description

• at gossip time, beaconBlocksMaybeBlobsByRoot() call range sync's matchBlockWithDataColumns() which is a mistake because we should not expect peer has enough columns for us at gossip time. Spec: https://github.com/ethereum/consensus-specs/blob/dev/specs/fulu/p2p-interface.md#datacolumnsidecarsbyroot-v1
• instead of that, just get as much columns as we can and return data promise at that time
• more details: bring matchBlockWithDataColumns() logic without matching code
• also this beaconBlocksMaybeBlobsByRoot() should not support multiple roots because:
  • consumer only need 1 root
  • from fulu, for each block peer may has different data for it at gossip time