Use latest jws & jwt functionality, add VC verify and decode functions to match #150

[KendallWeihe]

Background

This is a part of a messy multi-step multi-PR campaign to revamp JWS (#143), JWT (#144) and the uses in VC (#150); this PR addresses #150. I will subsequently open a PR removing all the non-v2 code and update bindings accordingly.

Changes

• Use the latest in the jwt crate (changes in Refactor jwt #144 #173) -- this includes RegisteredClaims, and the new sign/verify/decode functions
• Added VerifiableCredential::verify() and VerifiableCredential::decode() functions, as to match the paradigm with the latest in jws and jwt

Forward looking

• I'm not entirely sold on the way I have implemented the verify and decode so we can iterate on the approach there
• the same goes for VcJwtClaims
• Created this ticket to consider how we can support both VC Data Model 1.1 and 2.0 Consider differentiating between VC Data Models 1.1 and 2.0 #175 -- both of the above bullet points may be dependent upon how we think about supporting both data models
• in a subsequent PR I will remove all of the old code, and update bindings accordingly

[nitro-neal]

Eventually I think we will want a concept of a vcJwt as it is not exactly the same as a jwt

[nitro-neal]

for reference :

https://github.com/TBD54566975/web5-js/blob/main/packages/credentials/src/verifiable-credential.ts#L117C1-L134C4

  public async sign(options: VerifiableCredentialSignOptions): Promise<string> {
    const vcJwt: string = await Jwt.sign({
      signerDid : options.did,
      payload   : {
        vc  : this.vcDataModel,
        nbf : Math.floor(new Date(this.vcDataModel.issuanceDate).getTime() / 1000),
        jti : this.vcDataModel.id,
        iss : options.did.uri,
        sub : this.subject,
        iat : Math.floor(Date.now() / 1000),
        ...(this.vcDataModel.expirationDate && {
          exp: Math.floor(new Date(this.vcDataModel.expirationDate).getTime() / 1000),
        }),
      }
    });

    return vcJwt;
  }

[nitro-neal]

Ah perfect