feat: did module spec change through application of did document proof

[audtlr24]

Background

In aries-framework-go, DocumentSigner.Sign and VerifyProof methods are provided to verify the signature of the did document.

• DocumentSigner.Sign add Proof at did document using private key corresponding to public key of verificationMethod in did document.
• Information such as which verificationMethod to use and which encryption method to use can be defined through Signer.Context.
• VerifyProof verifies that the did document's proof field was created using the specified verificationMethod in the document.

Also, in the Proof of the document, there are Domain and Nonce that can replace the existing sequence to prevent replay-attack.

• We can specify this value in Signer.Context before document sign, and the proof value will be generated with different value depending on these.

Implementation

Remove the signature from the existing tx and replace it with the proof inside the document

• Since DID Ownership cannot be properly verified using only VerifyProof, additional verification is implemented in VerifyDIDOwnership.
• Since aries-framework-go uses ecdsa key, implement conversion parts with secp256k1 key used by panacea.

Remove the sequence part and change to use the Domain inside the document proof

• Domain is used because it is judged that the string Domain is more readable than the byte array Nonce.

Add a Deactivated field at DIDDocument and simply replace the related tx.

• In Deactivation, since there is no document update, it is simply changed to verify only the account signature.

[audtlr24]

I'm closing this PR in its current state. Since that aries is following a previous w3c spec and aries is not based on protobuf, it seems like a good idea to stick with the existing v2 x/did and not apply it right away.

I'll reopen it later if we need the various features of aries in a VC/VP-based datadeal model.