add VC checks

[bluesteens]

Steering: Proposal Summary

There are checks at VP level of VC properties. If there is a discrepancy between VC and VP, it will not be caught, as we do not check against the VC.

Steering: Publication Summary

Used to present completed work to Steering for approval to publish.
Discuss the work that was completed in reference to the above proposal. Include any differences from the proposal and why.
use [GitHub Preview](https://htmlpreview.github.io/) to show final state of documents along with pull requests (if needed).

---

Detailed Description:
We currently have these checks at VP level:

• the JWT field "exp" should represent the Credential Expiration Date
• the JWT field "nbf" should represent the Credential Issuance Date
• the JWT field "iat" should represent the VP generation date

We suggest to verify the credential fields in addition to the VP fields. We suggest to add these new checks to the OCI Wallet Criteria, since a wrongly formatted VP should not pass.

---

Triage:

• Is Issue appropriate for OCI Architecture
• Assign Size
• Assign Priority
• Assign Label (include Type of change and Steering "Review" or "FYI")
• OCI affected Artifacts Identified
• Assign Triage - Artifact Version Target (v x.x.x Milestone)
• Assign Triage - Interop Profile Version Target (v x.x.x Milestone)
• Create sub-project (if needed)

Affected Parties (help determine Sunrise/Sunset):

• Trading Partners
• Issuers
• Wallet Solutions
• PI Verification Solutions

Affected OCI Artifact

• Schema Document
• Identity Schema
• ATP Schema
• Issuer Conformance Criteria
• Wallet Conformance Criteria
• VRS Solution Conformance Criteria
• Wallet API Specification
• Governance Document
• Conformance Program
• OCI Website
• Internal Process

Change Category (Guides Steering Review)

- Steering/Industry Review

Needs Steering Consensus

• Business-Level (May affect business operations)
• OCI Governance, Policy or website feature

- Steering/Industry Notification

Does not need Steering Consensus (Steering may require a Consensus decision or futher clarification prior to issue being resolved by P&A

• Technical-Level (Does not affect business operations)
• OCI Internal Process or Infrastructure

Communication

• Website
• Newsletter
• email
• None
• Other:

[bluesteens]

P&A team decided to put this on hold to combine with other improvements