Reproducer:

1. Create a Physical Host, register it with portal with RHEL sub
2. Create guests on this physical host and configure virt-who to report the guests.
3. do conduit sync and then tally sync

There are two copies of hypervisors in System table API
On UI, two entries are shown for same hypervisor

Reference values for HardwareMeasurementType: https://github.com/RedHatInsights/rhsm-subscriptions/blob/develop/src/main/java/org/candlepin/subscriptions/db/model/HardwareMeasurementType.java

1. We need to start applying HardwareMeasurementType.HYPERVISOR (value was re-added but currently unused) as appropriate (please remove up redunant fields - a) HostBucketKey.asHypervisor, b) db.model.Host.isHypervisor).
2. We are currently providing a view that uses HostTallyBucket joined with Host; instead we need to fetch Host records and either lazy or eager fetch the associated HostTallyBuckets.
3. In order to show a host only once, please modify the hosts API to emit fields:

• sockets (total) - already exists, needs to be updated
• hypervisor_sockets
• physical_sockets
• virtual_sockets
• cloud_sockets

• cores (total) - already exists, needs to be updated
• hypervisor_cores
• physical_cores
• virtual_cores
• cloud_cores

There are the following use cases to be tested:

• non-RHEL hypervisor - only hypervisor_sockets and sockets non-zero.
• RHEL-based hypervisor - hypervisor_sockets, physical_sockets, and sockets non-zero (sockets = hypervisor_sockets + physical_sockets)
• Physical machine - only physical_sockets and sockets non-zero
• Cloud-based system - only cloud_sockets and sockets non-zero
• Guest with unknown hypervisor - only virtual_sockets and sockets non-zero

NOTE: if this needs to be split into multiple cards, please do so.