Test new runtime testing with intentionally-crashing runtime

[fredemmott]

To check for runtimes doing weird stuff (like setting DISABLE environment variables), master will launch a subprocess that does runtime discovery of API layers.

Should test unusable runtimes don't make this app unusable.

[fredemmott]

• if the runtime crashes in dllmain, it's ignored by the OpenXR loader, and xrEnumerate... still works

[fredemmott]

With this high-quality runtime:

#include <Windows.h>

#include <cinttypes>

BOOL WINAPI DllMain(
    HINSTANCE hinstDLL,
    DWORD fdwReason,
    LPVOID lpvReserved) {
  if (fdwReason != DLL_PROCESS_ATTACH) {
    return TRUE;
  }
  SetEnvironmentVariable("DISABLE_XR_APILAYER_ULTRALEAP_HAND_TRACKING_1", "");
  return TRUE;
}

extern "C" __declspec(dllexport) int xrNegotiateLoaderRuntimeInterface(
    void* loaderInfo,
    void* runtimeRequest) {
  OutputDebugStringA("Nullptr dereference\n");
  int* foo = nullptr;
  *foo = 123;
  return *foo;
}

Report includes:

❌ Bad exit code: 3221225477

.... which is HRESULT_ACCESS_VIOLATION, so expected