Render no-standard content-encoding response [INS-4910]

[yaoweiprc]

https://linear.app/insomnia/issue/INS-4910/support-custom-content-encoding
One of our customers reported that we couldn't render the response, the issue stems from the http response using the non-standard Content-Encoding header 'base64'. Currently, the libcurl library we use supports decompressing the response body with deflate, gzip, and br algorithms.

When the Content-Encoding response header uses a value other than deflate, gzip, or br, libcurl throws an error: "Unrecognized or bad HTTP Content or Transfer-Encoding", with error code 61.

At present, when libcurl throws the "Unrecognized or bad HTTP Content or Transfer-Encoding" error, we cannot retrieve the response body content.

To achieve the same behavior as Postman, we would first send a request. Upon encountering the "Unrecognized or bad HTTP Content or Transfer-Encoding" error, we would set ACCEPT_ENCODING in libcurl to null and resend the request. This way, libcurl will no longer throw the "Unrecognized or bad HTTP Content or Transfer-Encoding" error, and we can retrieve the compressed response body and Try to render it.