Feature Request: Move most VARBINARY columns to VARCHAR in examples

[mattlord]

Feature Description

The Vitess local examples (source) are a common first touch experience for users. These users are regularly confused or curious as to why many of the columns in the examples show up as HEX in the query results. The reason for this is that we use VARBINARY types throughout — in some rare cases like keyspace_id it makes sense, but most like customer.email are pure text. This makes understanding what's happening and quickly confirming at-a-glance results as expected more difficult and poses a minor hurdle when it's already quite a lot to get started with Vitess.

We should move most of our VARBINARY usage under ./examples to VARCHAR. This offers a more intuitive/expected experience while also more closely matching what users will be using for similar types of data.

Note: if any of those columns are used in Vindexes then we may also need to change the type used.

Use Case(s)

An easier on-ramp to Vitess.

[EraKin575]

I would like to work on this issue