Split up Verifiable Credential verify into its smallest parts for more granularity

## Verifications
These are all of the high level verifications that we will have modular access to for the api surface

* `verify`: Runs all verification checks.
* `verifyIntegrity`: Performs a JWT integrity check to ensure it adheres to expected formatting and contains all necessary elements. These include header verification, payload structure, and encoding checks.
* `verifySignature`: Cryptographic verification of the JWT's signature to confirm its authenticity. This involves resolving the issuer's DID, retrieving the corresponding public key, and using it to verify the signature against the JWT's payload. These include did resolution, signature verification and algorithm verification
* `verifyVcDataModel`: Verifies if it is a valid VC data model, confirming the VC's structural compliance with the relevant standards.
* `verifyExpiration`: Checks the VC expiration date to ensure it is still valid.
* `verifyStatus`: Checks if the status list credential exists and if it is valid or revoked.
* `verifySchema`: Ensures that the VC conforms to a specified schema.
* `verifyTrustedIssuer`: Will accept options for a list of trusted issuer dids :warning:

These functions can be public and work along side the VerificationOptions