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.

definitions/config.lua

@@ -10,5 +10,5 @@ local FulfillmentConfig
 ---@class Config
 ---@field fulfillment FulfillmentConfig
 ---@field devices DeviceInterface[]?
----@field schedule table<string, function>?
+---@field schedule table<string, fun() | fun()[]>?
 local Config

src/config.rs

@@ -1,6 +1,7 @@
 use std::collections::HashMap;
 use std::net::{Ipv4Addr, SocketAddr};
 
+use automation_lib::action_callback::ActionCallback;
 use automation_lib::device::Device;
 use automation_macro::LuaDeviceConfig;
 use lua_typed::Typed;
@@ -39,7 +40,7 @@ pub struct Config {
     pub devices: Vec<Box<dyn Device>>,
     #[device_config(from_lua, default)]
     #[typed(default)]
-    pub schedule: HashMap<String, mlua::Function>,
+    pub schedule: HashMap<String, ActionCallback<()>>,
 }
 
 impl From<FulfillmentConfig> for SocketAddr {

src/schedule.rs

@@ -1,10 +1,11 @@
 use std::collections::HashMap;
 use std::pin::Pin;
 
+use automation_lib::action_callback::ActionCallback;
 use tokio_cron_scheduler::{Job, JobScheduler, JobSchedulerError};
 
 pub async fn start_scheduler(
-    schedule: HashMap<String, mlua::Function>,
+    schedule: HashMap<String, ActionCallback<()>>,
 ) -> Result<(), JobSchedulerError> {
     let scheduler = JobScheduler::new().await?;
 
@@ -14,7 +15,7 @@ pub async fn start_scheduler(
                 let f = f.clone();
 
                 Box::pin(async move {
-                    f.call_async::<()>(()).await.unwrap();
+                    f.call(()).await;
                 })
             }
         };