Send a roboflow-python User-Agent on every SDK request

[iurisilvio]

What does this PR do?

Every HTTP request the SDK and the CLI make now sends User-Agent: roboflow-python/<version> (today roboflow-python/1.7.1). On main they send requests' default, python-requests/<version>, which any other Python client sends too, so SDK traffic can't be told apart in the API's request logs, which already record the User-Agent.

• roboflow/util/http.py (new): get, post, put, patch, delete, head and request wrap the requests functions of the same name and add the header. Headers the caller passes take precedence, including a User-Agent of its own. http.Session is a requests.Session that sends the header.
• Call sites: the 179 requests.<verb>(...) calls in 24 modules under roboflow/ call the helper of the same name, and so do the five Batch Processing adapters that hand requests.get/requests.post to _batch_processing_request. Workspace.search_export builds its session with http.Session(). The two urllib image fetches in roboflow/util/prediction.py send the header too.
• roboflow/__init__.py: __version__ moves to the top, so roboflow.util.http can read it while the package's imports run. setup.py reads it with a regex, which still matches.
• pyproject.toml: ruff's banned-api (TID251) rejects requests.get, post, put, patch, delete, head and request outside roboflow/util/http.py, with a message that names the helper to use instead. requests.Session stays allowed because type annotations use it.
• requests itself is not patched: code in the user's process that calls requests directly keeps its own User-Agent.

Two commits: the helper, then the switch of the call sites and tests, which is mechanical.

Related Issue(s): none.

Type of Change

• New feature (non-breaking change that adds functionality)

Testing

• I have tested this change locally
• I have added/updated tests for this change

Test details:

• tests/util/test_http.py:
  • each helper and http.Session send the header, the caller's headers are kept, and a caller's own User-Agent wins;
  • Roboflow() → workspace → project → version, and Project.upload with an annotation (the upload and annotate POSTs), send it on every request. Both fail when the header is dropped, and the upload test also fails if the upload goes through a plain requests.Session();
  • the hosted-image fetch in PredictionGroup.save sends it.
• Tests that mocked roboflow.<module>.requests.<verb> now mock roboflow.util.http.requests.<verb>, where the call happens (153 patch targets in 11 files, nothing else changed in them). The three tests that compared the whole headers dict now expect the User-Agent too.
• python -m unittest: 1241 tests OK, 1 skipped, on Python 3.12 and 3.10 (macOS). The slim job (requirements-slim.txt, then tests.test_slim_compat tests.test_vision_events) passes on 3.10. make check_code_quality passes (ruff 0.17.1, mypy 2.4.0).
• On the wire, against a local HTTP server set as API_URL: Roboflow(api_key=...) and roboflow --json auth status --api-key ... send python-requests/2.34.2 on main and roboflow-python/1.7.1 on this branch.
• Not run against staging or production.

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code where necessary, particularly in hard-to-understand areas
• My changes generate no new warnings or errors
• I have updated the documentation accordingly (if applicable): not applicable

Additional Context

• Reuse connections for image uploads and annotation saves, and retry failed annotation saves #558 sends image uploads and annotation saves through a per-thread requests.Session(). Whichever of the two PRs merges second should build that session with http.Session(); test_uploading_an_annotated_image fails until it does.
• The CLI sends the same User-Agent as the SDK.

🤖 Generated with Claude Code

[digaobarbosa]

LGTM