Enable retrieval of binary buffers

[guidiaz]

• In http/s sources, binary contents are specified by setting headers defined within MIME-type spec (RFC-2045). While data is serialized to text format during transmission, at client's app level is received as binary content.
• By enabling binary data at the Witnet protocol level, either hash() or toString() reducers would be available within data requests.

[tmpolaczyk]

The conversion from bytes to string is implemented here:

witnet-rust/rad/src/lib.rs

Lines 242 to 248 in 63920bd

	let response_string = response
	// TODO: replace with .body_bytes() and let RADON handle the encoding?
	.body_string()
	.await
	.map_err(|x| RadError::HttpOther {
	message: x.to_string(),
	})?;

We are using this method from the surf library, which only supports UTF8: https://docs.rs/surf/2.3.2/surf/struct.Response.html#method.body_string

There is a body_bytes method which returns the raw bytes: https://docs.rs/surf/2.3.2/surf/struct.Response.html#method.body_bytes

So we could add a check like:

• If the first operator of the script expects bytes as the input, use body_bytes
• Otherwise, use body_string

The only problem is that we cannot access the request headers from RADON to read the content type, so converting the bytes into a string later will only be possible if we know the encoding ahead of time when creating the script. Similarly, when converting string to bytes we need to specify an encoding somehow. But encodings other than UTF8 are not supported yet, so that can be another issue.

[Tommytrg]

Superseeded by #2331