Do not test VkDevice, VkInstance creation OOM paths in WSI tests
VkInstance and VkDevice creation OOM simulation is done already in
dEQP-VK.api.object_management.alloc_callback fail and repeating testing
in WSI tests just wastes time.
Since we want to trigger OOM even if implementation calls into instance-
or device-level callbacks, this is done by setting a mode in
DeterministicFailAllocator that stops alloc counting and failure
simulation.
Bug:
30811856
Change-Id: I9709b5eac98d8057a9080f12c07c8a2b76c83850