added appgen dag

[grallewellyn]

Purpose

This purpose of this PR is to publish a DAG that uses the Docker image running docker in docker to make packaging an algorithm: https://unity-sds.gitbook.io/docs/mdps-overview/tutorials/algorithms-and-algorithm-development/packaging-an-algorithm easier for users
I published the Docker image that we are using in the DAG to our jplmdps account: https://hub.docker.com/r/jplmdps/unity-app-gen

My code for the DAG and Dockerfile is here: unity-sds/unity-app-generator#31

Proposed Changes

• [ADD] Functioning AppGen DAG

Issues

Relevant issues:
unity-sds/unity-project-management#228
#275
unity-sds/unity-app-generator#21

Testing

• This is a successful run of the App Gen DAG: https://www.dev.mdps.mcp.nasa.gov:4443/graceal-4/dev/sps/dags/appgen_dag/grid?dag_run_id=manual__2025-04-09T20%3A37%3A53%2B00%3A00&task_id=appgen_task&tab=logs
  There are no tokens in the logs
  Note that this link might not be available after 4/9 since I have to tear down my Airflow deployment each night
• I tested the generated process.cwl file with a CWL DAG Modular

[LucaCinquini]

@grallewellyn : if you redeploy your SPS with the latest Docker image version (2.6.0 - as specified in the Airflow tfvars file) you will be able to simplify this DAG by importing POD_LABEL, DEFAULT_LOG_LEVEL and EC2_TYPES from the plugin file.

Additionally, there might not be a need to ask the user to select a disk size and EC2 type - should those be fixed to reasonable values that work for all app-generator jobs? Let's talk to @mcduffie about it.