Extend the HTTP API to cover all automation components readings

Greetings Beaverlords

The 1.0 HTTP API is a fantastic foundation — HTTP Levers and Adapters open up real creative possibilities. But the API currently only covers those two components, which limits what can be built externally.

Currently only HTTP Levers/Adapters are accessible. Sensors like Population Counter show "Measurement: 170" in-game but this value can't be read externally.

Proposed endpoints:

/api/sensors - read measurement values from all placed sensors
/api/relays - read logic gate output states
/api/timers - read timer states
/api/memory - read/set memory states
/api/levers - extend to regular levers (not just HTTP ones)

Also: include sensor measurement values in HTTP Adapter outbound calls.

This would unlock second-screen dashboards, remote automation control panels, smart home integrations, stream/Twitch interactions, and data logging. The automation system is brilliant — opening it to external tools would let the community extend it far beyond the game window.

TY