Align the DIDComm protocol implementation in the edge-agent SDK Swift with the DIDComm specification

[yshyn-iohk]

Is this a regression?

No

Description

All Aried protocols (e.g., issue credentials, present proof, revoke credentials, report a problem, etc.) should be revised according to the DIDCommV2 specification.

Please provide the exception or error you saw

1. Follow the [specification recommendation](https://identity.foundation/didcomm-messaging/spec/#:~:text=body%20%2D%20OPTIONAL.%20The,exist%20when%20receiving) for the`body`property: _to be fully compatible with DIDComm v2.0. It’s recommended always to have this attribute when sending a message, but allow the attribute not to exist when receiving._
2. Alight the internal properties of the `body` between the cloud agent and edge agents for each DIDCommV2 protocol and each message.
Example of the message: issue-credential/3.0/issue-credential

Please provide the environment you discovered this bug in

DEV

Anything else?

Interoperability with other SSI systems and agents needs to align with the specifications and not send unnecessary properties