fix: ignore state changes reported while a controller is being restored

[seydx]

Small one, found while working on the secure video controller but not specific to it.

What happens

ControllerStorage.restoreController calls controller.deserialize(), and most controllers restore their state through updateCharacteristic. That emits CHANGE. A controller listening on its own characteristics (or on a service it shares with another controller) reports a state change from inside the restore, handleStateChange serialises the controller mid-way and overwrites the stored data with the partially restored state. Whatever the controller restores after that point is gone on the next save.

CameraController doesn't trip over this because its listeners only react to HAP writes, but any SerializableController that uses CHANGE listeners does.

Fix

A restoring flag on ControllerStorage, set around deserialize() and around the initial restore loop in init(). State changes reported while it's set are ignored. The characteristics keep their restored values, only the write-back is skipped.

Test

ControllerStorage.spec.ts restores a controller that reports a state change halfway through its deserialize() and checks that the stored data is still complete, and that a real state change afterwards is picked up as usual.