fix: don't dump login traceback at ERROR for expected failures

login() used logger.exception() before re-raising a clean exception,
so every expected failure (rate limit, Cloudflare 403/CAPTCHA, all
strategies exhausted) printed a full stack trace at ERROR level on top
of the meaningful exception the caller already receives.

Downgrade to logger.debug() without exc_info — the breadcrumb survives
in debug mode, but callers get only the clean raised exception.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: cyberjunky

garminconnect/__init__.py

@@ -682,7 +682,9 @@ def login(self, /, tokenstore: str | None = None) -> tuple[str | None, str | Non
         ) as e:
             status = getattr(getattr(e, "response", None), "status_code", None)
             error_str = str(e).lower()
-            logger.exception("Login failed: %s (status=%s)", e, status)
+            # Re-raised below with a clean message; avoid logging a full
+            # traceback for expected failures (rate limits, bot challenges).
+            logger.debug("Login failed: %s (status=%s)", e, status)
 
             if status == 429 or "429" in error_str:
                 raise GarminConnectTooManyRequestsError(
@@ -718,7 +720,7 @@ def login(self, /, tokenstore: str | None = None) -> tuple[str | None, str | Non
                 raise GarminConnectAuthenticationError(
                     f"Authentication failed: {e}"
                 ) from e
-            logger.exception("Login failed")
+            logger.debug("Login failed: %s", e)
             raise GarminConnectConnectionError(f"Login failed: {e}") from e
 
     def resume_login(