scrypted: settings page /state fetch — sequence + 3s timeout

Two reasons the Status (live) section was showing
"offline / unreachable (fetch failed)" intermittently:

1. /state and /config were fetched in parallel, eating both available
   httpd sockets simultaneously (Phase 2 dropped max_open_sockets
   from 4 to 2). Any other inbound HTTP at the same instant would
   either queue or error.
2. The 1.5s timeout was tight given the firmware now juggles a live
   stream socket on port 81 (with occasional cap-flush reconnects)
   alongside the httpd workers on port 80.

Sequence the two fetches and bump the timeout to 3s. Total worst-case
6s if both are slow; that's fine for a Settings page, far from
"feels offline."

0 files changed, 0 insertions, 0 deletions