fix: use up-to-date `kid` in JWT header when refreshing
This PR is a variation on #3942 that attempts to solve the problem by letting fosite set the kid header of tokens and removing all of the code to explicitly set this header in JWTs.
Not sure if there's anything I should do about the CodeQL scanning results task failing. It seems spurious.
I pushed up three commits to restore the extra key, validate the UUID format, and remove some of the extraneous diff.
Also, please let me know how you'd like me to resolve conflicts, if at all. I can merge or rebase or squash at your preference.
I realized the checks wouldn't even run due to the conflict, so I rebased and squashed.
And, I think the CI jobs flaked, but I can't re-run them. 😞
@aeneasr anything more I can do here?
@aeneasr is it possible to get this change merged?