use did-communication service type in DID Exchange
The service type should be did-communication rather than IndyAgent in DID Exchange.
@sklump -- can you please take this? For 0160, it can remain as it was, but for DID Exchange, it should be this new format. Not sure if this data lies in the shared "connection object", which makes it more fun...
Related to this: https://github.com/decentralized-identity/didcomm-messaging/issues/179
This is covered in my draft PR here, where we leave it as IndyAgent for the connections protocol for compatibility with current .NET agents: https://github.com/hyperledger/aries-cloudagent-python/pull/1056
Closing this is being addressed in the PR for updating Unqualified DIDs to DID Peer.