top-level localdb status should show Syncing in addition to Active / Failure

[thedavidmeister]

Problem

The top-level `LOCALDB` indicator in the webapp sidebar collapses many per-chain states into one of two visible labels (`ACTIVE` or `FAILURE`). When chains are partway through their pipeline — manifest fetched, dumps downloading, engine running, etc. — the per-chain detail modal shows `SYNCING` but the sidebar badge does not reflect that state.

This means a user looking at the sidebar can't tell the difference between:

• All chains are healthy and idle (`ACTIVE`)
• All chains are healthy and busy bootstrapping / fetching / decoding (also surfaces as something other than `FAILURE` today)

If even one chain is mid-pipeline, the top-level badge should show `SYNCING` so the user knows the database isn't authoritative yet and will change as work completes.

Proposal

Add a `SYNCING` state to the top-level localdb status badge with priority below `FAILURE` and above `ACTIVE`:

• If any chain is in `FAILURE` → top-level badge shows `FAILURE` (existing behaviour).
• Else if any chain is in `SYNCING` (anything other than the steady-state idle/ready phase) → top-level badge shows `SYNCING`.
• Else → top-level badge shows `ACTIVE`.

Acceptance

• During an in-progress sync (e.g. immediately after registry refresh, dumps downloading, etc.), the sidebar `LOCALDB` badge reads `SYNCING` rather than `ACTIVE`.
• Once every chain reaches the post-sync ready state, the badge transitions to `ACTIVE`.
• When any chain fails, the badge shows `FAILURE` regardless of the others' progress.