Allow MockVM to run GC

[qinsoon]

This PR made some changes to MockVM to allow us to run GC in the tests.

• Add features mock_test_side_metadata and mock_test_header_metadata. We only test with mock_test_side_metadata (as some plans don't run with header metadata).
• No longer use lock for the MockVM instance (otherwise it will cause deadlock when we reentry MockVM)
• Statically initialize a MMTK instance for mock tests.
• Mock tests now use mock_api to create a mutator. This registers the mutator to mock VM, and can be blocked for GC.
• Mock tests now properly initialize GC threads, and handle panics in GC threads.
• Minor changes to print more information for mmap failures.

[wks]

std::sync::ReentrantLock is an unstable feature. But a third-party crate parking_lot has an implementation of ReentrantMutex. If that is helpful, we can add the parking_lot as a dependency when the mock_test feature is enabled.

[wks]

This is where I think Option<NonZeroAddress> can be useful. See #1223

[wks]

Currently ObjectReference is required to be aligned to ObjectReference::ALIGNMENT. So even if VM::MIN_ALIGNMENT is smaller than ObjectReference::ALIGNMENT, VO bits can only be set at addresses which are multiples of ObjectReference::ALIGNMENT. I think the algorithm here is wrong (or just outdated). It is pointless to increment the cursor by VM::MIN_ALIGNMENT. It should simply align the cursor up to the next multiple of ObjectReference::ALIGNMENT. And I wonder whether find_last_non_zero_bit_in_metadata_bytes could be more efficient (needs to search forward instead of backward).