presentation-exchange spec review

[manicprogrammer]

This review of presentation-exchange is called out specifically separate, in this instance, from the normal maintenance review. The reason for this is that the Abstract section specifically states:

The specification is designed to be both claim format and transport envelope agnostic, meaning an implementer can use JSON Web Tokens (JWTs), Verifiable Credentials (VCs), JWT-VCs, or any other claim format, and convey them via Open ID Connect, DIDComm, Credential Handler API, or any other transport envelope.

yet the map shows dependencies on OIDC, CHAPI, JWT etc. It is believed the map is wrong and needs to be corrected.
This issue drives the effort for a new review of presentation-exchange specifically with the outcome of either correcting the mapping or finding it is correct and putting in an issue for the correction of the abstract on the presentation-exchange document.

[manicprogrammer]

Converted all the connections for presentation-exchange except vc-data-model to references connection type and label. Also added a new reference link to ld-cryptosuite-registry.

[manicprogrammer]

Released in v1.3.2