feat: fix async handling in jwt verify

[lukasjhan]

I found a bug while developing https://sdjwt.co

in jwt verify method, It doesn't wait until its resolved. verifier can be async function so we need await keyword.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.39%. Comparing base (c65744c) to head (b513e15).

Additional details and impacted files

@@           Coverage Diff           @@
##             next     #131   +/-   ##
=======================================
  Coverage   97.39%   97.39%           
=======================================
  Files          23       23           
  Lines        1878     1878           
  Branches      272      273    +1     
=======================================
  Hits         1829     1829           
  Misses         49       49           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[cre8]

Lgtm,

Have you also checked the code if we have other mistreated async calls?

And I think all defined functions that can be passed to the sd-jwt instance should be async, since we don't know if the user needs it for his implementations. Or we define some type like Promise<string> | string

[lukasjhan]

Lgtm,

Have you also checked the code if we have other mistreated async calls?

And I think all defined functions that can be passed to the sd-jwt instance should be async, since we don't know if the user needs it for his implementations. Or we define some type like Promise<string> | string

Yeah, I checked all code in core :) I guess now we're good.
Currently we treated passed functions as OrPromise which is Promise | type.