[MAINT] Upgrade go-jose to v4

[deiga]

Resolves #3350

---

Before the change?

• We we're using deprecated v3 of go-jose

After the change?

• We are now using v4 of go-jose and can prepare for upcoming release of v5

Pull request checklist

• Schema migrations have been created if needed (example)
• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)

Does this introduce a breaking change?

Please see our docs on breaking changes to help!

• Yes
• No

---

[github-actions]

👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with Status: Up for grabs. You & others like you are the reason all of this works! So thank you & happy coding! 🚀

[stevehipwell]

@deiga could you rebase this? I assume you've run the tests locally?

We ought to update the PR checklist to capture if tests have been run locally with a box to put the output in.

[deiga]

@stevehipwell Would that fit into this PR? #3261

Yeah, I'll rebase. And I had run all test that use go-jose features

[stevehipwell]

LGTM

[stevehipwell]

@deiga it looks like @robert-crandall isn't currently online (based on Slack). I think we're OK to merge the Dependabot updates with an approval from both of us, so shall we do those and then you can rebase this PR afterwards?

[stevehipwell]

@deiga could you please rebase this PR?

[deiga]

@stevehipwell Done

[stevehipwell]

LGTM

[stevehipwell]

@robert-crandall could you please approve this (or let us know that for changes like this you're happy for us to have a single maintainer approval)?