urQueueCreateWithNativeHandle shouldn't allow hDevice to be null

[hdelan]

Associating a ur_queue_handle_t with a ur_context_handle_t is sort of meaningless if we are using a multi device context, as the context doesn't tell us which device in the context the queue should be associated with. As such I think we should not allow the hDevice param to be null.

[aarongreig]

If we do change this it should be a relatively trivial change on the UR side, but it will almost certainly break sycl RT's make_queue implementation https://github.com/intel/llvm/blob/sycl/sycl/include/sycl/backend.hpp#L354 https://github.com/intel/llvm/blob/sycl/sycl/source/backend.cpp#L116 we had a lot of that kind of issue when we ported to UR and turned on the validation layer: sycl loves to pass nullptr to CreateWithNative type entry points - which is probably why null was allowed here in the first place. To my untrained eye it looks like you'd need to do a "get first device in context" thing on the sycl side to remediate, which is really just shuffling the nastiness up a layer rather than doing away with it.