Fix output for binary keys in -verbose mode. (#1559)

When migrating a table with a `binary` key in `-verbose` mode, different
sequences of bytes may prevent execution output from being logged, or
correctly logged, to the console.

This happens because the `MigrationRange*Values` are printed to the
screen without any type of encoding. One particularly problematic
sequence is `0x27`, `Escape`, which causes the terminal to stop logging
for the duration of the migration:

```
2025-05-23 11:53:27 INFO Listening on unix socket file: /tmp/gh-ost.test.binfoo.sock
2025-05-23 11:53:27 INFO Intercepted changelog state ReadMigrationRangeValues
2025-05-23 11:53:27 INFO Handled changelog state ReadMigrationRangeValues
2025-05-23 11:53:27 INFO Migration min values: [
```

This commit changes the to-string rendering for `binary` keys, rendering
the values as a hex string rather than an unescaped series of bytes.

Co-authored-by: meiji163 <meiji163@github.com>

Author: burnison

go/sql/types.go

@@ -325,7 +325,7 @@ func (this *ColumnValues) AbstractValues() []interface{} {
 func (this *ColumnValues) StringColumn(index int) string {
 	val := this.AbstractValues()[index]
 	if ints, ok := val.([]uint8); ok {
-		return string(ints)
+		return fmt.Sprintf("%x", ints)
 	}
 	return fmt.Sprintf("%+v", val)
 }

go/sql/types_test.go

@@ -40,3 +40,12 @@ func TestGetColumn(t *testing.T) {
 		require.Nil(t, column)
 	}
 }
+
+func TestBinaryToString(t *testing.T) {
+	id := []uint8{0x1b, 0x99}
+	col := make([]interface{}, 1)
+	col[0] = id
+	cv := ToColumnValues(col)
+
+	require.Equal(t, "1b99", cv.StringColumn(0))
+}