Use Nipoppy schema to validate proc status TSV for bagel derivatives command

[alyssadai]

When users come to us with an imaging status file - whether made by nipoppy or made by hand - we would like to validate the file against the current Nipoppy schema to make sure the contents have the correct structure. The Nipoppy schema is written in pydantic, so we will have to decide how we want to "ingest" the schema in our own tools.

Some options are:

• copy paste the pydantic schema directly into our codebase
• make nipoppy itself a dependency of the cli so we can directly import the schema
• find ways to export the schema in a format that encompasses all of its validation functions and that we can read in
• spin out the schema into a separate repo (e.g. pipeline catalog?) and then consume it from there (e.g. via submodule)

[alyssadai]

Currently blocked by #180, due to Nipoppy schema being written in v2 (and we would have to use their model as a module, not jsonschema, due to the internal validation they have)

Edit: No longer blocked

[surchs]

Tracked while we discuss how to do this
edit: will discuss this Thursday and then issue either goes into a milestone or off the board

[surchs]

Decision: We will implement the following as part of a new issue: grab example imaging status file from a nipoppy maintained repo (e.g. catalog) and use it as a test target. Keep this example in sync with upstream nipoppy (e.g. submodule) so tests start breaking when we go out of sync