…d CLI.

PiperOrigin-RevId: 1019531612

PiperOrigin-RevId: 1019609843

…ThinkingLevel

PiperOrigin-RevId: 1019626832

PiperOrigin-RevId: 1019666937

`test_custom_client.py`, `test_client_close.py` and `test_aiohttp_retries.py` set the module-level `_api_client.has_aiohttp` flag but never restored it. When `aiohttp` is not installed, `test_constructor_with_httpx_clients` left the flag at `True`, so async uploads in later tests on the same pytest-xdist worker took the aiohttp path and failed with `NameError: name 'aiohttp' is not defined` (for example `tests/gaos/test_environments_lifecycle.py::test_python_environments_async_file_upload_download`). Which tests shared a worker depended on how many tests were collected, so the failure came and went with unrelated changes.

Replace the per-file `reset_has_aiohttp` fixtures with a single autouse fixture in `tests/client/conftest.py`. It saves the original value and restores it after every client test. The old fixtures in `test_async_stream.py`, `test_client_initialization.py` and `test_retries.py` forced the flag to `False` instead, which turned aiohttp off for later tests when it is installed.

Two tests depended on that forced `False` without setting it. `test_client_initializes_httpx_clients_vertex_and_mldev` and `test_vertexai_with_httpx2` now set `has_aiohttp = False` themselves.

Also fix `test_constructor_with_httpx_clients`, which checked `_use_aiohttp()` on the Gemini Developer API client twice and never on the Vertex AI client.

PiperOrigin-RevId: 1019680062

PiperOrigin-RevId: 1020280180

Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>