verify that byte arrays are handled consistently

Byte array fields are treated in some ways like repeated fields.
- They are stored in a mutable List
- hasField() returns false if they're empty.
- an empty byte array doesn't change the hashCode (versus null)

In other ways they're treated differently: you can use setField() to replace a byte array.
It seems like the corner cases need to be tested better, particular for events.