Mismatched row access sizes in tests

The RowEncoderSuite and UnsafeMapSuite tests fail on big-endian systems. This is because the test data is written into the row using unsafe operations with one size and then read back using a different size. For example, in UnsafeMapSuite the test data is written using putLong and then read back using getInt. This happens to work on little-endian systems but these differences appear to be typos and cause the tests to fail on big-endian systems.

I have a patch that fixes the issue.