For tables with the same name in different libraries, the field order is not consistent

[Xuxiaotuan]

For tables with the same name in different libraries, the field order is not consistent and there is no constraint.

Question：

mysql-binlog-stream/binlog-stream/app/io/laserdisc/mysql/binlog/stream/TransactionState.scala

Line 64 in 2b7ede9

transactionState.schemaMetadata.tables

     case (EventHeaderV4(EventType.TABLE_MAP, _, offset), TableMapEventData(tableId, name)) =>
          transactionState.schemaMetadata.tables
            .get(name)
            .foreach(transactionState.schemaMetadata.idToTable(tableId) = _)
          (transactionState.copy(offset = offset), None)

The result is that different ids have the same table name and field order but are not consistent

java.lang.ClassCastException: java.lang.Long cannot be cast to [B
at io.laserdisc.mysql.binlog.stream.TransactionState$.$anonfun$mapRawToMeta$1(TransactionState.scala:364)
at scala.collection.ArrayOps$.map$extension(ArrayOps.scala:929)
at io.laserdisc.mysql.binlog.stream.TransactionState$.recordToJson(TransactionState.scala:353)
at io.laserdisc.mysql.binlog.stream.TransactionState$.convertToJson(TransactionState.scala:301)
at io.laserdisc.mysql.binlog.stream.TransactionState$.$anonfun$handleCreate$3(TransactionState.scala:134)

So I added schema check

[barryoneill]

Hi @Xuxiaotuan - thank you for this contribution. I've added some test coverage that I believe covers the situation.