fix: report a pump as running from its telemetry, not its STATUS

[hacctarr]

The PUMP binary sensor treats STATUS == "10" as running. On both of my PUMP/VSF pumps, STATUS sits at 10 whether or not the pump is turning, so both sensors read on permanently.

Two pumps read at the same moment, straight out of /api/states:

entity	STATUS	RPM	PWR	GPM	sensor	actual
binary_sensor.filter (PMP01)	10	3068	1300	53	on	running
binary_sensor.spa_jets (PMP02)	10	0	0	0	on	idle

The controller also never pushes STATUS for a pump. Only the telemetry:

NotifyList {"objectList":[{"objnam":"PMP01","params":{"RPM":"3069"}}]}
NotifyList {"objectList":[{"objnam":"PMP01","params":{"PWR":"1306"}}]}

So a STATUS-keyed isUpdated never fires when a pump starts or stops, even on a system where STATUS does move.

PumpBinarySensor derives is_on from whichever of RPM, PWR, and GPM the pump publishes, and keys isUpdated on the same attributes. A pump that publishes none of them falls back to the STATUS comparison, so single speed pumps are untouched. The unique_id is unchanged and existing entities carry over. Device class becomes RUNNING.

Running on 2.0.0 against my own IntelliCenter, binary_sensor.spa_jets now reads off while binary_sensor.filter stays on, and the debug log shows the entity updating off the telemetry it now keys on:

updating <entity binary_sensor.filter=on> from {'PMP01': {'RPM': '3069'}}
updating <entity binary_sensor.filter=on> from {'PMP01': {'PWR': '1306'}}