1056760: Support guestids with reverse-endianness

## Mismatched Endianness in ESX Guest UUID
### The Problem
Although we have not yet been able to reproduce the issue, some versions of ESXi are reporting guest uuids that differ from the guests dmi uuid.

### But how?
Uuids are built in part using information from the local system, and in part using changing information (time).  Only the first part seems to be read differently between the guest system and the hypervisors api.

Example:
```
78d7e200-b7d6-4cfe-b7a9-5700e8094df3
00e2d778-d6b7-fe4c-b7a9-5700e8094df3
```

### The Fix
Any time we query for a host or guest consumer record given
a uuid type identifier, we will search using both the id as given
as well as a transformed uuid where the first three sections
are reversed-endian.

### Additional Info
* https://www.vmware.com/support/vsphere5/doc/vsphere-esxi-51u1-release-notes.html
* http://howtowriteaprogram.blogspot.cz/2009/03/uuid-and-byte-order.html
Could we check the host on each of these guests as well to make sure the reverse query is working in real world test.