Specify validations / verifications for processing VCs

[decentralgabe]

          Do we want to really nail down specifically what validations / verifications here or elsewhere in the doc or is this too granular for this doc?

This is what we have in the issue I created for this:

Verification Processes

• verify: Runs all verification checks.

• verifyIntegrity: Performs a JWT integrity check to ensure proper formatting and inclusion of all necessary elements such as header, payload structure, and encoding checks.

• verifySignature: Cryptographically verifies the JWT's signature to confirm authenticity, involving issuer's DID resolution, public key retrieval, signature, and algorithm verification.

• verifyVcDataModel: Confirms the VC's structural compliance with relevant standards, verifying its validity as per the VC data model.

• verifyExpiration: Checks the VC expiration date to ensure validity.

• verifyStatus: Verifies the existence and validity of the status list credential, checking for revocation.

• verifySchema: Ensures VC adherence to a specified schema.

• verifyTrustedIssuer: Accepts options for a list of trusted issuer DIDs, ⚠️.

Originally posted by @nitro-neal in #122 (comment)

[angiejones]

@EbonyLouis let's track this issue and update the VC Verify guide accordingly