Trino VARBINARY columns should scan to []byte slices instead of strings.

[ademille]

Trino columns that are VARBINARY type are base64 encoded before being sent via HTTP to the go client. The current client implementation scans the data into a 'string' type without base64 decoding the values, forcing the user of the driver to do an extra non-intuitive base64 decode to get the original binary data back.

It would be better to have the driver perform the base64 decode and return a []byte slice.
For example, if an IP address or MAC address is stored as a varbinary column in trino, the client could return a []byte type which could be used to create a net.IP or net.HardwareAddr directly.

[fatpa]

use from_utf8({varbinary_data}) function can return base64 decode data