hallow-cli logging to account for lambda issues

[chapem]

(Flagging this after going down a rabbit hole that ended up being caused by one of the actions-built zips (which when downloaded is named hallow.zip.zip btw) being corrupt somehow. Building from source fixed that issue.)

The hallow-cli logging is displayed in a way that makes it seem as if the respondent json, exit code, and error message comes directly from the hallow webserver, with a client-side hard coded "internal server error" for catchall failures:

FATA[0000] Got a non-200 exit code                       error="hallow/client: HTTP error from hallow. Status=502: {\"message\": \"Internal server error\"}" hallow.endpoint="someendpoint" hallow.publi
c_key.comment=somecomment hallow.public_key.type=ecdsa-sha2-nistp384

A great addition to hallow-cli would be to explicitly display where a log message comes from, whether an issue is lambda, hallow, or local environment/parsing related. Thanks in advance.