fix(memory) BinaryVector fixes for M1 Mac

[amolnayak311]

Issue
On Mac M1, incNumBytes has a quirk. The operation fails with SIGBUS when a getAndAddInt is invoked on an address offset that is one of the three preceding every multiple of 16. For e.g when addrs is 13, 14, 15, 29, 30, 31, 45, 46, 47 byte offset from the base address, the operation UnsafeUtils.unsafe.getAndAddInt(UnsafeUtils.ZeroPointer, addr, inc) fails. However, when we do a get and put non atomically, it works. The fix is done to currently unblock developers from using M1 Mac. However, the fix is far from ideal as the data written to the block of memory by FiloDB is application specific and the block of memory is opaque to the operating system, in other words, the OS should not be interpreting this data as long as the application is working on the block it is allocated.

IMPORTANT
The PR is built on top of this PR #1428 by @kvpetrov.

Next steps
Once the issue with UnsafeUtils.unsafe.getAndAddInt(UnsafeUtils.ZeroPointer, addr, inc) is identified, the changes to BinaryVector.incNumBytes will be reverted.

[vishramachandran]

Approved, Thanks for digging into this!