Message compatibility on graphsync

[hannahhoward]

Goals

We currently support data transfer protocols v1_1 & v1_0 at the libp2p level, but we weren't properly handling them as extensions to graphsync

Implementation

• define named Graphsync extensions for 1_0 & 1_1
• when opening channels or sending messages in extensions, where possible, always write both versions
• when reading graphsync requests and checking for extensions, prioritize 1_1 if present, but read 1_0 if not
• add a config options in setting up the graphsync transport so that we can turn of 1_0/1_1 extensions as needed
• setup integrations tests to ALSO test graphsync sending only certain types of extensions
• verified in practice also with real client/miner running different versions of protocol
• also update to tagged go-graphsync