Avoid over-allocation of bytes for UTF8 string serialization

In the current message encoding implementation, it first calculates the `encodeSize` and allocates the bytebuffer with that size.

However, during encoding, it assumes the worst case of writing UTF8 string to allocate bytes, i.e. assuming each letter takes 3 bytes.

The over-estimation further leads to resizing the underlying array and data copy.