feat: Use ActionCallback for schedule

This has two advantages:
- Each schedule entry can take either a single function or table of
  functions.
- We get a better type definition.

automation_lib/src/device.rs

@@ -27,7 +27,7 @@ impl mlua::FromLua for Box<dyn Device> {
     fn from_lua(value: mlua::Value, _lua: &mlua::Lua) -> mlua::Result<Self> {
         match value {
             mlua::Value::UserData(ud) => {
-                let ud = if ud.is::<Self>() {
+                let ud = if ud.is::<Box<dyn Device>>() {
                     ud
                 } else {
                     ud.call_method::<_>("__box", ())?
@@ -36,10 +36,7 @@ impl mlua::FromLua for Box<dyn Device> {
                 let b = ud.borrow::<Self>()?.clone();
                 Ok(b)
             }
-            _ => Err(mlua::Error::runtime(format!(
-                "Expected user data, instead found: {}",
-                value.type_name()
-            ))),
+            _ => Err(mlua::Error::RuntimeError("Expected user data".into())),
         }
     }
 }

src/bin/generate_definitions.rs

@@ -32,7 +32,7 @@ fn config_definitions() -> String {
     output +=
         &FulfillmentConfig::generate_full().expect("FulfillmentConfig should have a definition");
     output += "\n";
-    output += &Config::generate_full().expect("Config should have a definition");
+    output += &Config::generate_full().expect("FulfillmentConfig should have a definition");
 
     output
 }