fix: correctly parse JWT ValidMethods from env by enabling split_words

[singh-inder]

What kind of change does this PR introduce?

Bug fix

What is the current behavior?

JWT ValidMethods not parsed from env because split_words was missing on the struct tag, causing envconfig to look for GOTRUE_JWT_VALIDMETHODS instead of GOTRUE_JWT_VALID_METHODS. Since v2.71.1, cli defaults to asymmetric keys, which caused valid HS256 tokens to be rejected.

What is the new behavior?

This change adds split_words to ensure the correct env var is used. I assume that GOTRUE_JWT_VALID_METHODS is the correct env var but if it isn't, then this issue can also be solved by updating the env var passed to auth service in supabase cli to

			env = append(env, "GOTRUE_JWT_VALIDMETHODS=HS256,RS256,ES256")

Additional context

The following screenshots are from print statements I added

1. config.JWT.ValidMethods was nil because it was looking for wrong env var. It defaulted to jwk key algorithm (ES256).
   

   auth/internal/conf/configuration.go

   Lines 1092 to 1097 in 645654d

   	if config.JWT.ValidMethods == nil {
   	config.JWT.ValidMethods = []string{}
   	for _, key := range config.JWT.Keys {
   	alg := GetSigningAlg(key.PublicKey)
   	config.JWT.ValidMethods = append(config.JWT.ValidMethods, alg.Alg())
   	}

   
   
   

2. After
   

[singh-inder]

Maybe related:
https://github.com/orgs/supabase/discussions/41895
supabase/cli#4726

[coveralls]

Pull Request Test Coverage Report for Build 21084248505

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

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

---

Totals
Change from base Build 21060916988:	0.0%
Covered Lines:	14724
Relevant Lines:	21491

---

💛 - Coveralls

[aantti]

Also supabase/cli#4524 ?

[aantti]

@hf @kangmingtay

[aantti]

Possibly also supabase/supabase#42037