hipDeviceGetUuid is not compatible with VkPhysicalDeviceIDProperties::deviceUUID

[Snektron]

As the title suggests, hipDeviceGetUuid returns a different UUID than VkPhysicalDeviceIDProperties::deviceUUID. These IDs are needed to relate two devices from the different APIs to eachother, so as to ensure that the same is chosen when doing interop.

It seems that both in the Mesa and AMDVLK drivers, this ID is derived from the PCI bus address and so is compatible with each other (even if only by accident), while in hip it is via rocr derived from unique_id in /sys/devices/virtual/kfd/kfd/topology/nodes/*/properties, which is ultimately created from the device's serial number (at least on some architectures).