feat: honour ONTAP_TIMEOUT env var in OntapClient.from_env()

[algojogacor]

Summary

Honour ONTAP_TIMEOUT environment variable in OntapClient.from_env(), allowing users to configure the request timeout without modifying code.

Changes

• python/ontap_client.py: from_env() now reads optional ONTAP_TIMEOUT env var (defaults to 30s) and passes it as timeout= to the constructor. Docstring updated accordingly.
• python/README.md: Added ONTAP_TIMEOUT documentation with usage examples for CI and slow clusters.

Testing

# With ONTAP_TIMEOUT set to 2s, connection to unreachable host fails fast
ONTAP_HOST=10.0.0.1 ONTAP_PASS=x ONTAP_TIMEOUT=2 python cluster_info.py
# ~2s timeout (was 30s)

# Without ONTAP_TIMEOUT, behavior is unchanged (30s default)
ONTAP_HOST=10.0.0.1 ONTAP_PASS=x python cluster_info.py
# ~30s timeout (unchanged)

Closes #35

[github-actions]

Test Report missing or unfilled.

This PR touches python/, ansible/, or terraform/, so a populated Test Report section is required in the PR body. See TESTING.md for what to capture (environment, platform version, first-run output, idempotency check, teardown).

This is a soft gate - your CI checks are unaffected - but reviewers will not approve until the report is filled in.

[github-actions]

Thanks for your first PR to Pace — welcome aboard.

Quick orientation:

1. CI runs in ~2 minutes. If anything fails, check the Actions tab — most failures have a one-line fix in docs/troubleshooting.md.
2. If your PR touches python/, ansible/, or terraform/, you'll be asked for a Test Report. It's worth the effort — reviewers rely on it.
3. Make sure the NetApp CCLA is on file before review.
4. Stuck? Comment on this PR and a maintainer will jump in. We aim to respond as soon as possible.

For background, see CONTRIBUTING.md.