Garth

Related to https://github.com/tcgoetz/GarminDB/issues/192#issuecomment-1742136941

PR 17

The requirement of Pydantic >=2 was creating a dependency conflict as reported in https://github.com/cyberjunky/python-garminconnect/issues/162. We now support Pydantic >=1.10.13 (as tested).

Issues: https://github.com/matin/garth/issues/14 and https://github.com/cyberjunky/python-garminconnect/issues/162
PR: 15

There are instances where the upload URL needs to be set. This release now allows for `path` to be passed as an argument but retains the same default path.

This release adds `garth.client.upload()`

python
with open("12129115726_ACTIVITY.fit", "rb") as f:
uploaded = garth.client.upload(f)


Issue 8
PR 9

Inline with [0.4.30](https://github.com/matin/garth/releases/tag/0.4.30), this release uses the same timeout set in `garth.configure()` in `GarminOAuth1Session`.

garth.http.Client.sess` uses `requests.Session` and has `proxies`, `verify` and `adapters` set. For part of the login, `garth.sso` uses `requests_oauthlib.OAuth1Session`. The `proxies` and `verify` were being set but not the `adapters`, which include retry (including backoff) logic.

Specifically for `OAuth1Session` (as subclassed by `GarminOAuth1Session`), this release makes setting `proxies` and `verify` more DRY and uses the same https:// adapter as the main Garth session.

Given the use of `garth.sso` by other projects, I want to make sure it's bulletproof and will continue to find ways to improve it.