Transaction log threshold should be checking Transaction message size, not Statement

[David Shrewsbury]

Transaction services code currently assumes that a Transaction message will ever only have a single Statement when checking for message size threshold and uses Statement::ByteSize(). This is fine for bulk inserts, but not true when a long transaction contains a hodge-podge of mixed statements. Fix is to use Transaction::ByteSize() instead.