Add PDAF to workflow engine

[jjokella]

Plan: Introduce PDAF as a modelid in the workflow engine in the different steps:

• Initialization (run by user before starting WFE, possibly also integrated somewhere)

  • provide input files ("common"/"cesm")
  • provide static files, possibly perturbed
  • provide parameter files, possibly perturbed
  • provide the case namelist files and stream files (single case, best in a repository / based on template)
  • provide TSMP-PDAF control file enkfpf.par HPSCTerrSys/PDAF_input-file-generator
  • provide observation files HPSCTerrSys/PDAF_observation-file-generator

• Preprocessing (pre)

  • atmospheric forcing generation (via CLM-modelid), need to check that this works together with perturbation step
  • atmospheric forcing perturbation using HPSCTerrSys/eCLM_atm-forcing-generator
  • future, possibly: soil parameter perturbation, perturbation of further parameters, but currently this would be part of an initial step that needs to be present before the WFE starts

• Simulations (sim)

  • ensemble namelist creation could be part of sim_config or initialization
  • jobscript needs to get tsmp-pdaf run-command option

• Postprocessing (pos) -> future

• Visualization (vis) -> future