Fix flaky HTTPS integration test

[jsturtevant]

The HTTPS integration test depended on httpbin.org and intermittently failed when the service returned transient 503 responses.

Use this repository's GitHub page as the real TLS endpoint and retry transport errors or 5xx responses up to three times with exponential backoff (250 ms, then 500 ms). Non-retryable HTTP responses still fail immediately, and the test continues to validate a successful HTTPS response and expected body content.

[Copilot]

Pull request overview

This PR aims to reduce flakiness in the HTTPS integration test by removing reliance on httpbin.org and introducing retry behavior for transient failures, while still validating a successful HTTPS response and expected body content.

Changes:

• Switched the HTTPS test target from httpbin.org to a GitHub-hosted HTTPS endpoint.
• Added retry logic (up to 3 attempts) with exponential backoff (250ms → 500ms) for transport errors and 5xx responses.

Suppressed comments (1)

src/hyperlight_sandbox/tests/http_integration.rs:140

• If switching to a static raw file endpoint, the body assertion should match stable file content (e.g., the Apache 2.0 header) instead of relying on GitHub’s repo-page HTML.

                    assert_eq!(resp.status, 200);
                    assert!(String::from_utf8_lossy(&resp.body).contains("hyperlight-sandbox"));

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.