Update crypto-suite names

[Wind4Greg]

This PR updates the cryptography suite names to conform to VC-Data Integrity specification.

This PR does not change the content of the examples or test vectors. Those will be updated after this PR is accepted and merged.

---

Preview | Diff

[dmitrizagidulin]

👍 thanks for doing this!

[OR13]

This a subtle change, but I believe it reflects well working group consensus on this topic at the previous face to face, and it highlights an important extension point for data integrity proofs.

[msporny]

@OR13 wrote:

This a subtle change, but I believe it reflects well working group consensus on this topic at the previous face to face, and it highlights an important extension point for data integrity proofs.

Alright, good, then looks like we have consensus on this topic.

@Wind4Greg @dmitrizagidulin @iherman -- we need to register a new cryptosuite type in the security vocabulary for DataIntegrityProofs such that we can compress these longer strings into single byte values during semantic compression processes like what's used by CBOR-LD. I've opened w3c/vc-data-integrity#161 to track this concern, which doesn't need to hold up this PR.

[msporny]

Normative, multiple reviews, no changes requested, no objections, merging.

[msporny]

Now that this is merged, @Wind4Greg, let's make a pass over all the cryptosuites and apply the naming uniformly over all of them, merge the sec:cryptosuiteString feature, regenerate all of the test vectors and finally be done with all of this. :)

[Wind4Greg]

Agree @msporny. Will review all for consistency. Have new test vectors ready to integrate into the documents.