Re-introduce human-readable chip types
Re-introduce human-readable chip types

The chip label generation has been changed in #334 to prefer the
unique device path (e.g. the location on the PCI bus) due to #333.

Here, a new annotation metric ``node_hwmon_chip_names`` is
introduced which allows to link the unique chip sysfs path to a
human-readable chip name which may not be unique among chip sysfs
paths (for example, dual-slot systems have multiple
chipType="coretemp" sensors).

This allows to mitigate the downsides of the solution to #333
(namely that the device path may not be stable across kernels and
reboots) for cases where it does not matter that multiple devices
may have the same human-readable name (e.g. aggregation or where
at most one device with a common chip name is present).

For cases where no human-readable name can be derived, the
annotation metric is not emitted.

Jean-Daniel/node_exporter,siavashs/node_exporter,siavashs/node_exporter,knweiss/node_exporter,chosenken/node_exporter,knweiss/node_exporter,siavashs/node_exporter,siavashs/node_exporter,joehandzik/node_exporter,bs-github/node_exporter,joehandzik/node_exporter,prometheus/node_exporter,ema/node_exporter,prometheus/node_exporter,joehandzik/node_exporter,prometheus/node_exporter,derekmarcotte/node_exporter,chosenken/node_exporter,Jean-Daniel/node_exporter,chosenken/node_exporter,derekmarcotte/node_exporter,bs-github/node_exporter,derekmarcotte/node_exporter,bs-github/node_exporter,derekmarcotte/node_exporter,joehandzik/node_exporter,ema/node_exporter,knweiss/node_exporter,Jean-Daniel/node_exporter,ema/node_exporter,chosenken/node_exporter,bs-github/node_exporter,Jean-Daniel/node_exporter,knweiss/node_exporter,ema/node_exporter