Evaluate creating "tamper" sensors for each sensor

[xaf]

Pros:

• Clear sensor identifying if another sensor is currently tampered
• Possible to disable by default a sensor, but keep its tamper enabled by default (e.g. for sensors that do not update a state, but do support tamper)

Cons:

• A lot more sensors showing in Home Assistant, more noisy
• Huge internal refactor as a single QolsysSensor object might lead to more than one sensor sent to MQTT
• Breaking change (we could probably keep, but deprecate, the tamper attribute for a few versions)

[jsb5151]

IMHO, I don't think this is feasible due to #117 - multiple loop sensors will most likely always create phantom Tampered conditions when another sensor is triggered on the same device.