SDK: More resilient HTTPStatus errors

[lucaspar]

Non-standard 499 (Client Closed Request) errors were raising ValueError.

---

Note

Low Risk
Localized error-handling change with tests; no auth or data-path behavior change beyond avoiding crashes on uncommon status codes.

Overview
Non-standard HTTP response codes (e.g. nginx 499) no longer crash the SDK when HTTPStatus(code) raises ValueError.

The PR adds _safe_http_status, which returns a normal HTTPStatus when possible or a small _SyntheticHTTPStatus fallback with the same is_success / is_client_error / is_server_error helpers. success_or_raise and GatewayClient.authenticate now use this helper instead of constructing HTTPStatus directly, so errors are classified and raised as SDSError, ServiceError, etc., with the API error body. Tests cover 499 (client) and 599 (server).

^{Reviewed by Cursor Bugbot for commit 691abeb. Configure here.}

[semanticdiff-com]

Review changes with  

Changed Files

File	Status
sdk/src/spectrumx/gateway.py	0% smaller
sdk/src/spectrumx/ops/network.py	0% smaller
sdk/tests/ops/test_network.py	0% smaller

[mjcurran]

@klpoland Does this PR warrant another SDK version release? I was assuming so, but I don't know if there's a schedule to follow, or other criteria for when a release is deployed to pypi.