cli: does not properly respect the bytea_output setting for displaying BYTEA values

[rafiss]

Describe the problem

The cockroach cli shows BYTEA values in a go-escaped format, which is difficult to work with if you want to use the value by copy/pasting it into a different SQL command.

To Reproduce

Connect to a CRDB cluster using cockroach sql and run:

root@:26257/defaultdb> select descriptor from system.descriptor limit 1;
                                                                      descriptor
-------------------------------------------------------------------------------------------------------------------------------------------------------
  \x129\n\x06system\x10\x01\x1a%\n\r\n\x05admin\x10\x80\x10\x18\x80\x10\n\f\n\x04root\x10\x80\x10\x18\x80\x10\x12\x04node\x18\x02"\x00(\x01@\x00J\x00

Expected behavior
If you connect using psql to the same cluster, you get:

defaultdb=> select descriptor from system.descriptor limit 1;
                                                        descriptor
--------------------------------------------------------------------------------------------------------------------------
 \x12390a0673797374656d10011a250a0d0a0561646d696e1080101880100a0c0a04726f6f7410801018801012046e6f646518022200280140004a00

Environment:

• CockroachDB commit dbbe9ed

Additional context
Using a cast like select descriptor::text from system.descriptor limit 1; does work correctly.

@knz points out that the behavior is a limitation of lib/pq, see:

cockroach/pkg/cli/clisqlexec/format_value.go

Lines 90 to 106 in 11a0a9f

	case []byte:
	// Format the bytes as per bytea_output = escape.
	//
	// We use the "escape" format here because it enables printing
	// readable strings as-is -- the default hex format would always
	// render as hexadecimal digits. The escape format is also more
	// compact.
	//
	// TODO(knz): this formatting is unfortunate/incorrect, and exists
	// only because lib/pq incorrectly interprets the bytes received
	// from the server. The proper behavior would be for the driver to
	// not interpret the bytes and for us here to print that as-is, so
	// that we can let the user see and control the result using
	// `bytea_output`.
	var buf bytes.Buffer
	lexbase.EncodeSQLBytesInner(&buf, string(t))
	return buf.String()

Moving the CLI to use pgx could help address this issue.

Jira issue: CRDB-15625