Reset HTTP client connection after unknown error responses

[Keith-wright]

Summary

• Calls reset_all on the HTTP client after receiving an unknown/unexpected status code, ensuring subsequent requests get a clean connection
• Known response codes handled by the library (200, 202, 400, 401, 403, 404, 407, 413) are treated as clean HTTP exchanges and do not trigger a reset
• Fixes an issue where an unexpected server response could leave the connection in a state that caused the next request to fail

Thanks to @rmosolgo for reporting and following up on this.

Closes #193

Changelog

• [FIXED] Reset HTTP client connection after unknown error responses to prevent subsequent requests from failing.

[aonemd]

Thanks @Keith-wright!