Detect chip ID / family where possible to improve auto-detection rejection of wrong sensors

Testing the latest batch of added sensors, most of them are identified incorrectly at auto-detection (HTU31d becomes INA219 etc).
Looking deeper most of the begin calls we don't confirm the chip ID, so we could in some instances. Those drivers should then come first in the list of sensors to try for the specific i2c addresses.

Start by reviewing the sensor drivers' begin calls and the auto-detection logic described in the issue. Identify which drivers can confirm a chip ID or family and how sensor candidates are ordered for each I2C address. Done means supported IDs are checked where possible, wrong sensors such as HTU31D and INA219 are rejected, and the relevant drivers are tried first.

Written by the indexing model from the issue text.