Include Bitswap into request response protocols

[altonen]

Include bitswap protocol into the list of enabled request response protocols. Previously the code stored the bitswap into another vector stored in sc_network::config::Params but didn't extend the protocol vector that contained the protocols that were given to Behaviour, essentially leaving Bitswap disabled even if --ipfs-server was provided on the command line.

[altonen]

bot merge

[alebaffa]

Hi, sorry to comment on this after 3 months, but I also found this issue (still open) paritytech/polkadot-sdk#542 where it is said that

Ok, then request-response can't be used for implementing bitswap because it requires opening a new stream for each response.

So, this PR means that it is no more the case?
Thanks.

[sinkingsugar]

This didn't fix much.
substrate side we receive requests from ipfs clients, but ipfs clients never get substrate responses currently.

[altonen]

@alebaffa @sinkingsugar

Looking at this implementation of Bitswap protocol, it would lead me to believe we can implement the protocol over the request response protocol meaning there might be some discrepancy between the "right way" and our way of implementing the codec. I'll look into how we might go about fixing this.

[altonen]

Unfortunately it seems that the Bitswap protocol cannot be built on top of the request response protocol if we want to be compatible with go-ipfs and js-ipfs. There is a way for us to add support for the protocol while keeping it still as a generic protocol living above sc-network, issue paritytech/polkadot-sdk#524 tracks the progress of this