fix: Home Assistant: use "occupancy" device_class for human presence sensors

[jspiros]

This addresses a semantic difference in how the term "presence" is used by Home Assistant. Home Assistant uses the "presence" device_class for binary_sensor entities that track the presence of something mobile or portable. To that end, Home Assistant reports state changes in binary_sensor entities with the "presence" device_class like "binary_sensor was detected at home" or "binary_sensor was detected away".

I have verified that all devices currently supported by zigbee2mqtt that expose a "presence" sensor are human presence sensors (sensors that detect the presence of a person or people in a physical space) which is a more appropriate use case for the "occupancy" device_class in Home Assistant.

State changes in binary_sensor entities with the "occupancy" device_class are reported by Home Assistant like "binary_sensor detected occupancy" or "binary_sensor cleared (no occupancy detected)", which is a much more coherent message for these sensors.

[codspeed-hq]

CodSpeed Performance Report

Merging #28329 will not alter performance

_{Comparing jspiros:ha-presence-occupancy (e1ad3b1) with dev (23f831a)}

Summary

✅ 9 untouched benchmarks

[Koenkk]

Thanks!