Some desktop VR headsets don't work with openxr backend and provide no feedback

[jdm]

Blair reported that he has an older Samsung Odyssey than the Odyssey+ that I have, and the x64 FxR didn't do anything for him when he pressed the button to enter immersive mode on a three.js demo. The app kept working, but the canvas stopped animating and the headset didn't show immersive mode. We should add more logging so it's easier to tell what's going on, and the engine shouldn't pretend it's in immersive mode if there's an error on the webxr thread.

[jdm]

From an instrumented build running with an older Odyssey:

RUST: WARN - webxr::openxr - requesting openxr device session
RUST: WARN - webxr_api::registry - XR device error BackendSpecific("Entry::create_instance ERROR_INSTANCE_LOST")
RUST: WARN - webxr_api::registry - no device could support the session
RUST: WARN - script::dom::xrsystem - Error requesting XR session: NoMatchingDevice