Incorrect name of Kafka Schema for values, doesn't match schema for keys

The MySQL connector in Debezium 0.2 generates a Kafka Connect (and ultimately Avro) schema for the before and after fields in the event message envelope with a name that is missing a delimiter.

This is a big deal and needs to be fixed, but doing so would mean any envelopes produced with 0.2.1 or 0.3 would be with a different schema than with 0.2, and this would likely make a mess for downstream consumers. Ideally, this means that *Debezium 0.2 should not be used*, but it if is then clients will simply have to deal with the change in schema for any persisted messages.