feat: support allow_expired query parameter for JWT validation

[mandarini]

Description

Adds support for allow_expired=true query parameter to allow decoding expired JWTs for legitimate use cases (debugging, audit logs, displaying user info after expiration).

Fixes: #2256

Changes

• Modified parseJWTClaims() in internal/api/auth.go to check for allow_expired query parameter
• When allow_expired=true, JWT parser skips claims validation (including expiration check)
• Default behavior unchanged: JWTs are validated including expiration by default

Security Considerations

• The JWT signature is still verified (not bypassed)
• Only the expiration time check is skipped
• This should be used only for specific legitimate use cases
• The client library (supabase-js) will control when this parameter is passed

Testing

Tested with expired JWTs:

• Without parameter: correctly rejects with expiration error
• With allow_expired=true: successfully decodes and returns user data
• Signature validation still enforced in both cases

[cstockton]

@mandarini Are you still wanting to implement this? If you are we will need a greater refactor here because parseJWTClaims is shared by areas of code which must respect JWT expiration.