UI: Config Key Editor with Individual Get/Set

[rodneyosodo]

Summary

The backend will support persistent config with individual key get/set via MQTT (#26) and an allowlisted key system (#34). The current Config page is a flat form that POSTs the entire config object. It should be replaced with a key-value editor that mirrors the MQTT config get/config set interface.

What to build

• Replace or extend the current ConfigCard component
• Fetch the list of configurable keys from the backend (or a known allowlist)
• For each key, show:
  • Key name
  • Current value (with a "fetch" button)
  • Edit inline with a "save" button
• Credential keys (passwords, secrets) should show masked values with a reveal toggle
• Show not_allowed / not_found status messages from the backend
• Group keys by category (connection, channels, intervals, credentials)

Depends on

• Persistent Config Store with Remote Get/Set #26 (Persistent Config Store)
• Config Key Allowlist and Credential Protection #34 (Config Key Allowlist and Credential Protection)

Reference

Aeolus config get/set format (docs/control.md):

[{"n":"config","vs":"get,telemetry_interval"}]
[{"n":"config","vs":"set,telemetry_interval,10"}]

Response: [{"n":"config_telemetry_interval","vs":"30"}]