feat: add hybrid jwt verification

[kallebysantos]

What kind of change does this PR introduce?

Bug fix, feature

What is the current behavior?

Since API keys did change, users can't call functions without manually disabling verify_jwt.

What is the new behavior?

JWKs are now default exposed #4688, so It allows to verify both new asymmetric tokens as well legacy ones.

This way it applies a temporary fix while migrating API keys.

• closes JWT key verification broken (Edge Runtime 1.7.0+) for self-hosted deployments edge-runtime#654
• solves ES256 JWT verification fails in Edge Functions after CLI upgrade to 2.72.6 supabase#41929

[coveralls]

Pull Request Test Coverage Report for Build 20992742862

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 7 unchanged lines in 2 files lost coverage.
• Overall coverage remained the same at 56.148%

---

Files with Coverage Reduction	New Missed Lines	%
internal/storage/rm/rm.go	2	80.61%
internal/gen/keys/keys.go	5	12.9%

Totals
Change from base Build 20983346857:	0.0%
Covered Lines:	6850
Relevant Lines:	12200

---

💛 - Coveralls