SIPNET workflow for restarting with events

[ashiklom]

Prototype of running SIPNET with event files that include changes in crops. A few implementation notes:

• This supports PEcAn ensemble inputs (including for events)

• event.json files for multiple ensemble members are stored in run$inputs$events$source. SIPNET-specific event.in files are stored in run$inputs$events$path (like other inputs). This is because the current functionality for finding segments to split the runs uses the JSON files. @infotroph 's subset_paths function from an earlier draft has been adapted and modified to subset both path and source paths (as long as they have the same lengths).

• This circumvents runModule.start.model.runs and uses a direct execution loop instead. However, the output is PEcAn standard and follows PEcAn configuration conventions, so downstream analyses/workflows should work out of the box.

It's a bit hacky, but I think it does what it's supposed to and should be enough to unblock other CCMMF modeling tasks (@dlebauer).

[ashiklom]

OK, I think I've resolved all of @divine7022 and @infotroph comments. I also resolved a significant bug with write_events.SIPNET (namely, the events were always being written out in the same order as events.json, not sorted by date as intended), and did a bit of other miscellaneous cleanup.

Note that this PR sits on top of #3836 and #3828 --- if we merge this, we can probably just close those.

@dlebauer :

Great work! Excited to have this working! 🥳

Before merging, please create a ticket to cover the refactoring plan we discussed last week.

From what I recall, the plan was approximately:

Goal: refactor segmented runs so that they integrate more cleanly with standard start_model_runs workflows.

Specifically:

* write.configs generates config files

* sites and ensembles run in parallel via start_model_runs

* This will require modifying or replacing the top‑level job.sh so that:
  
  * Segments run sequentially within a site, and
  * Sites still run in parallel via start_model_runs.

All of this already works in this PR. The new write_segmented_configs.SIPNET does a bunch of config preparation behind the scenes and then modifies the job.sh files associated with each ensemble member such that, instead of running SIPNET directly, they run the segments in sequence and then post-process the results. This means that the actual interface here is very "PEcAn-ic":

settings <- PEcAn.workflow::runModule.run.write.configs(
  settings_raw,
  input_design = sens_design$X
)

source("workflows/sipnet-restart-workflow/utils.R")
jobfiles <- write_segmented_configs.SIPNET(settings, sens_design$X, force_rerun = TRUE)

PEcAn.workflow::runModule_start_model_runs(settings)

Whatever method the user has specified for running job.sh files in settings will continue to work here without modification.

[infotroph]

This looks great! I was able to run through 3 ensembled sites in a lightly modified MAGiC ensemble workflow using just utils.R with the changes noted below. I think this is ready to merge. Next iteration can be to decide which package(s) to drop the functions into.

[dlebauer]

I thought this table was with the landiq code. If not, I think @infotroph , @sarahkanee , and I have each implemented one or more versions of this mapping. And there is one in https://github.com/ccmmf/cadwr-landuse/blob/eacec3ba471b80ed3fc9404d300767f5b12a3654/data/CARB_PFTs_table.csv#L66 ... that doesn't meet the need here, but we can add columns (probably can have multiple pft cols representing different levels of splits, or could have a many-many table)