Add custom request timeout support for VWS and CloudRecoService

[adamtheturtle]

Summary

Adds support for configurable request timeouts in both VWS and CloudRecoService APIs. Previously, timeouts were hardcoded to 30 seconds. Now users can specify a custom timeout during client initialization.

Changes

• Add optional request_timeout_seconds parameter to VWS and CloudRecoService constructors with 30-second default
• Replace hardcoded timeout values with the configurable parameter
• Add comprehensive tests for both default and custom timeout behavior

Testing

Tests verify that the default timeout is 30 seconds and that custom timeouts can be set and used successfully.

---

Note

Low Risk
Small, backwards-compatible change that only affects HTTP request timeout configuration and adds targeted tests; main risk is behavioral change if callers relied on the fixed 30s timeout.

Overview
Adds an optional request_timeout_seconds parameter to VWS and CloudRecoService constructors (defaulting to 30s) and threads it through to the underlying requests.request calls, replacing the previously hardcoded timeout.

Expands test coverage in test_vws.py and test_query.py to verify both default timeout behavior and custom timeout values (including (connect, read) tuples), and documents the change in CHANGELOG.rst.

^{Written by Cursor Bugbot for commit a69677c. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}