feat: Trusted certificates hook for presentations

[Tommylans]

Gives the ability to dynamically set the trusted Certificates for a specific proof request.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9d1e18c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[TimoGlastra]

I had to think for a bit on what I think of this API. And I think it may be a bit confusing. Especially since correlationId is something internal to sphereon libraries, and proofRecordId it's not obvious this is for DIDcomm.

So.. what if we make it a verificationContext, which is optional, and has a unified interface that can be reused.

interface VerificationContext {
  /**
   * The `id` of the `ProofRecord` that this verification is bound to.
   */
  didcommProofRecordId?: string

  /**
   * The `id` of the `OpenId4VcVerificationSessionRecord` that this verification is bound to.
   */
   openId4VcVerificationSessionId?: string
}

I think we could also extract the trustedCertificates, but it would be good to also add these, as then you can pass them when calling the top-level APIs (w3c verification) (i think Sd-JWT is already possible right?)

And we will only call the get trusted certificates method if you didn't provide certificates (so if you call sdJWt.verify with certificates we won't call it). But otherwise we will

[Tommylans]

We can also add the already given trustedCertificates here so it's the choice by the user to combine it with the hook ones or completely override them

[TimoGlastra]

I like the general appraoch. Just some commetns to make it a bit more specific / unified and so we can extend it with other records as well in the future (e.g. issuance will also need this probably)

[TimoGlastra]

one final remark, otherwise LGTM!