Windows memory query to find the size fails on weird AllocationBase behavior on GA Server16

This was hit in Dr. Memory https://github.com/DynamoRIO/drmemory/issues/2328

The details are here: https://github.com/DynamoRIO/drmemory/issues/2328#issuecomment-739454412

Basically we have a case where the AllocationBase goes up and then drops back to an original value, and the query loop inside query_memory_internal() (which implements dr_query_memory()) fails when the AllocationBase doesn't match. This causes multiple address space walks in Dr. Memory to fail early, causing Umbra init to mess up, and leak scanning to assert.