fix: pass JWK for singing so that KeyID is set in JWTs

[mitar]

It is harder to validate generated JWTs because currently they do not include a key ID in the header. Even when key ID exists in the JWK used for signing. The reason is that Fosite currently removes this metadata information, but it is not necessary to remove it, our signing library uses it and knows how to use JWKs, even more, it adds key ID automatically if it is available and provided with a JWK.

Checklist

• I have read the contributing guidelines and signed the CLA.
• I have referenced an issue containing the design document if my change introduces a new feature.
• I have read the security policy.
• I confirm that this pull request does not address a security vulnerability.
  If this pull request addresses a security vulnerability,
  I confirm that I got approval (please contact [email protected]) from the maintainers to push the changes.
• I have added tests that prove my fix is effective or that my feature works.
• I have added the necessary documentation within the code base (if appropriate).

[tilgovi]

@aeneasr is there anything I can do to help get this released and update ory/hydra to use it? I think this is blocking ory/hydra#3573.

[aeneasr]

We accept PRs!

[tilgovi]

@aeneasr I can't PR a release here, can I?

[tilgovi]

If you can make a fosite release, I think my team can work on the PR to update Hydra and fix ory/hydra#3573.