Decode using HTTP::Response

HTTP::Response supports more types of Content-Encoding than URIFetch currently does, and it also decodes charset encoding which is not done at all by URIFetch.
This change will now use HTTP::Response to decode content.

This will allow OpenIDs for Yahoo! to work correctly.