Hookup for log/event messages to history server

[amitschang]

To utilize the existing history server for logs in addition to sensor data, the following steps were taken:

• namespace all included loggers with the package name. This is done so we can modify the logger without affecting root
• add a log handler class that emits to the history API
• add a hookup between the above two within the device manager, along with config options
• modify the history api to take a "kind" and "vial" parameter - kind differentiates between sensor reads and logs, and vial enables logs to be tied to a specific vial
• change shape of sensor data to be row-per-vial, instead of row containing struct of vials (will require corresponding UI mod)

Resolves: #131, Resolves #196
Enables/relates to: #109, #132

Some examples:

curl -Hcontent-type:application/json -XPOST localhost:8080/history/'?t_start=1732570420&t_stop=1732570440' -d'{"kinds": ["event", "sensor"], "vials": [0, 1]}' | jq .

{
  "data": {
    "test": [
      {
        "timestamp": 1732570421.0073779,
        "kind": "sensor",
        "vial": 0,
        "data": {
          "name": "NoOpSensorDriver",
          "vial": 0,
          "raw": 1,
          "value": 2
        }
      },
      {
        "timestamp": 1732570421.009811,
        "kind": "sensor",
        "vial": 1,
        "data": {
          "name": "NoOpSensorDriver",
          "vial": 1,
          "raw": 1,
          "value": 2
        }
      }
    ]
  }
}

curl -Hcontent-type:application/json -XPOST localhost:8080/history/'?n_max=2' -d'{"kinds": ["log"]}
' | jq . 

{
  "data": {
    "test": [
      {
        "timestamp": 1732569561.055786,
        "kind": "log",
        "vial": null,
        "data": {
          "level": "WARNING",
          "message": "test from HW"
        }
      }
    ],
    "evolver": [
      {
        "timestamp": 1732569561.033202,
        "kind": "log",
        "vial": null,
        "data": {
          "level": "ERROR",
          "message": "Error in loop: committing proposals for <MagicMock spec='EffectorDriver' id='4987471824'>"
        }
      }
    ]
  }
}

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

📢 Thoughts on this report? Let us know!

[jamienoss]

LGTM 👍

Just some comments/suggestions.

[jamienoss]

[comment] I can see this being duplicated if logging is needed from somewhere else. It would be better if self.history.put could handle this.

[jamienoss]

[comment] This would benefit from having a description.

[jamienoss]

[comment] It might help the TODO implementer if we added here and now, how we might envision coding this, e.g., using a match, an enum, a mapping etc?

[jamienoss]

[comment] It might be slightly more robust against future changes if we added a setting for this rather than relying on the convention of it always being __package__.
E.g.:

# evolver.settings
class Settings(...):
  ROOT_LOGGER_NAME: str = __package__

[amitschang]

Thanks. I made some corresponding changes, I think scope of them is small enough I will consider approval sticky and merge this in 😄