feat: return providing peer(s) in `bitswap:want-block:block` event

### Question

> Using Helia, when I download the contents of a CID, could I easily see which node I ultimately retrieved the data from? How would I do that?
> - @TheDiscordian

### Answer

> This could be added to bitswap - the hasBlock method [here](https://github.com/ipfs/js-ipfs-bitswap/blob/79974a5b165d84b878f25bb11ac63639d4e3e093/src/notifications.ts#L34C3-L38) would need the id of the providing peer added as an argument, then the bitswap:want-block:block event could hold both the CID of the incoming block and the providing peer when it's emitted [here](https://github.com/ipfs/js-ipfs-bitswap/blob/79974a5b165d84b878f25bb11ac63639d4e3e093/src/notifications.ts#L67).
>
> It's worth noting that if the DAG referenced by a CID is made from multiple blocks, these blocks could come from different peers, so it'd be more like "which node(s)" rather than "which node".
> - @achingbrain

This question came across in ip-js channel on slack: https://filecoinproject.slack.com/archives/C046HDAHA13/p1689877647075909