fix: don't blame the IP in login 429 messages

[cyberjunky]

Garmin's login endpoints also return 429 based on the client fingerprint (seen on IPs that were never used before), so "IP rate limited by Garmin" sent users chasing IP cooldowns. Rewords the mobile-login and all-strategies-rate-limited messages. Exception types are unchanged.

Reported in #444. The API-session change suggested there is intentionally not included (see the discussion on the issue).

Summary by CodeRabbit

• Bug Fixes
  • Clarified login error messages to explain that access may be limited based on the client or network, including client fingerprinting.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration

Configuration used: Repository: cyberjunky/python-garminconnect/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Advanced

Run ID: c58cbc9b-c67b-4edb-bba8-27942ba65e75

📥 Commits

Reviewing files that changed from the base of the PR and between 337d1f9 and e77ad56.

📒 Files selected for processing (1)

• garminconnect/client.py

 __________________________________________________________
< This abstraction leaks more than a sieve in a rainstorm. >
 ----------------------------------------------------------
  \
   \   \
        \ /\
        ( )
      .( o ).

✨ Finishing Touches

📝 Generate docstrings

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}