scrypted: 5s HTTP timeout + don't relaunch active stream on every event

Two changes to handle a burst of motion events without piling up
startStream calls and tripping the 1s /state-POST timeout:

- HTTP_TIMEOUT_MS 1000 → 5000. The firmware's single httpd task
  processes one TCP connection at a time; under heavy /frame streaming
  a /state {wake} can queue behind 1–3 in-flight /frames before
  landing. 1s was too tight.

- handleCameraEvent now ignores repeat triggers if a stream is already
  live for that viewport (this.streams.has(name)) or already starting
  (streamStarting set). Sustained motion fires MotionSensor every
  ~500ms; we used to launch a fresh startStream each time, racing
  with the previous one's ffmpeg spawn + state POST.

0 files changed, 0 insertions, 0 deletions