Translate,Utils,GoogleTranslate: add HTTPS/TLS support via curl

[tsaitang404]

Problem

trans returns [ERROR] Null response. for all translation requests:

$ trans :en "hello"
[ERROR] Null response.
[ERROR] Oops! Something went wrong and I can not translate it for you :(

Root cause: gawk's /inet/tcp does not support TLS. googleInit() sets HttpProtocol = "http://" on port 80, but translate.googleapis.com now requires HTTPS. The plaintext TCP connection returns an empty response, triggering the null assert.

Direct curl to the same endpoint succeeds:

$ curl -s "https://translate.googleapis.com/translate_a/single?client=gtx&sl=auto&tl=en&dt=t&q=hello"
[[["hello","hello",...]]]

Fix

• GoogleTranslate: switch to https:// on port 443
• initHttpService: when HttpProtocol == "https://", set UseHttps = 1 and skip gawk TCP init (which has no TLS support)
• getResponse: when UseHttps, build the full URL and delegate to new curlGetResponse()
• postResponse: when UseHttps, delegate to existing curlPost()
• Utils: add curlGetResponse() with full --proxy / --cookie / --user-agent support, consistent with the existing curl() function

The approach is generic: any other engine requiring HTTPS only needs to set HttpProtocol = "https://" in its *Init() function.

Copyright

I dedicate this contribution to the public domain under the terms of the Unlicense, consistent with this project's license.