Use moo schema for algorithm configuration parameters.

[BenLand100]

Currently the configure methods for Trigger*Maker accept raw nlohmann::json objects containing their configurations, and anything using these must create the correct structure to configure the algorithm. It would be better if these algorithms could define a schema for their configuration using moo, similar to DUNE DAQModules. This needs to be done such that no dependency on daq-cmake is introduced, so triggeralgs can still be built and used outside of a daq software environment.

[brettviren]

A very good idea.

To avoid dependency on daq-cmake I think here is one case where committing the generated files to a repo is okay. Because moo codegen is idempotent, the generated header files will only change when the developer actually modifies their schema (no repo bloat for inconsequential changes). This will not only erase daq-cmake as a build-time dependency but moo itself will not be needed to build the project.