[Go]: Not providing an `authToken` leads to opaque "Authorization header not provided"

I just spent 2 days diagnosing this issue, so I'm putting this here so others are a bit luckier. I used https://github.com/joho/godotenv + a .env file with an authentication token to a Turso DB, but forgot to call godotenv.Load() so my DB URL looked something like:

"libsql://[name]-[user].turso.io?authToken="

I'd have expected something like this to lead to a more transparent error (e.g. "no auth token provided" or something), as "Authorization header not provided" led me to think there was something wrong with SQLx instead.

Not sure if there is anything to fix here, but I hope this helps someone avoid wasting days of sanity over such a stupid mistake, lol.

Great product btw!

No files, tests, or entry points are identified. Start by tracing the Go authentication handling for a database URL with an empty authToken and determine where the generic authorization error is produced. Done means the missing-token case reports a clear, actionable error and is covered by a regression test.