Initial WiredTiger tasks DB implementation

Tests pass, but uncovered some maybe-bugs in the scheduler around forked tasks.

(Also design problem when reconstituting... these tasks need a Session that isn't NoopSession if they do background `notify` events. But how to get one?)

crates/daemon/src/main.rs

@@ -36,7 +36,7 @@ use crate::rpc_server::zmq_loop;
 
 #[cfg(feature = "relbox")]
 use moor_db_relbox::RelBoxDatabaseBuilder;
-use moor_kernel::tasks::NoopTasksDb;
+use moor_kernel::tasks::{TasksDb};
 
 mod connections;
 
@@ -45,6 +45,7 @@ mod connections_rb;
 mod connections_wt;
 mod rpc_server;
 mod rpc_session;
+mod tasks_wt;
 
 #[macro_export]
 macro_rules! clap_enum_variants {
@@ -84,6 +85,16 @@ struct Args {
     )]
     connections_file: PathBuf,
 
+    #[arg(
+        short = 'x',
+        long,
+        value_name = "tasks-db",
+        help = "Path to persistent tasks database to use or create",
+        value_hint = ValueHint::FilePath,
+        default_value = "tasks.db"
+    )]
+    tasks_db: PathBuf,
+
     #[arg(
         long,
         value_name = "rpc-listen",
@@ -271,7 +282,17 @@ fn main() -> Result<(), Report> {
         textdump_output: args.textdump_out,
     };
 
-    let tasks_db = Box::new(NoopTasksDb {});
+    let tasks_db: Box<dyn TasksDb> = match args.db_flavour {
+        DatabaseFlavour::WiredTiger => {
+            let (tasks_db, _) = tasks_wt::WiredTigerTasksDb::open(Some(&args.tasks_db));
+            Box::new(tasks_db)
+        }
+        #[cfg(feature = "relbox")]
+        DatabaseFlavour::RelBox => {
+            warn!("RelBox does not support tasks persistence yet. Using a no-op tasks database. Suspended tasks will not resume on restart.");
+            Box::new(NoopTasksDb {})
+        }
+    };
 
     // The pieces from core we're going to use:
     //   Our DB.