Post-Quantum (PQ) and Post-Quantum/Traditional (PQ/T) hybrid signatures for VCs

[AleCla97]

Description of change

Integration of Post-Quantum (PQ) and Post-Quantum/Traditional (PQ/T) hybrid signatures for VCs

• New features: pqc for PQ related code, hybrid for hybrid related code, pqc-liboqs for the pq signatures implementation based on liboqs, hybrid-liboqs for the hybrid signatures implementation, based on this draft
• JwkStoragePQ: Extension of the JwkStorage for pq keys and Memstore implementation
• Algorithm Key Pair (AKP), new Jwktype for PQ JWKs based on ML-DSA for JOSE and COSE
  draft
• CompositeAlgId: Hybrid keytype MLDSA44/65-ED25519
• DID JWK extension: create a new DID JWK with traditional, pq, hybrid and zk keys
• DIDCompositeJWK, did method for hybrid keys and his relative resolver
• JwtCredentialValidatorHybrid and JwtPresentationValidatorHybrid, hybrid signature validators
• PQCJwsVerifier, verifier for PQ signatures with an implementation based on liboqs
• New examples: pq and hybrid
• Wasm: bindings of the new functions
• Wasm: new examples: pq and hybrid
• Wasm: JwkPqMemStore and PQJwsVerifier implementation of JwkStorage and IJwsVerifier with noble post quantum for ML-DSA

Other changes

• Bump zkryptium and json proof token version to match the latest BBS and JPT drafts

Type of change

Add an x to the boxes that are relevant to your changes.

• Bug fix (a non-breaking change which fixes an issue)
• Enhancement (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Fix

How the change has been tested

• cargo test --release to see that there were no incompatibilities.
• the new features were tested through the new pq and hybrid tests( both rust and wasm.)
• the update of zkryptium and json proof token was also tested by running the zkp tests

Change checklist

Add an x to the boxes that are relevant to your changes.

• I have followed the contribution guidelines for this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes