Lin 547 implement parameterization for framework airflow pipeline with params setup

[mingjerli]

Description

On top of LIN-566 refactor airflow jinja template, this PR implements parameterized pipeline for airflow (for both PythonOperatorPerArtifact and PythonOperatorPerSession flavor).

During implementation, it also discovered and fixed the issue that all user input parameter types are cast to string in the Python module via argparse, since we found a similar issue with Airflow params.

Fixes # (issue)

LIN-547 LIN-566

Type of change

Please delete options that are not relevant.

• [x] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?

• Add new tests for both flavors of airflow parameterized pipeline.
  • Locally test the dag can run in Airflow with user-defined parameters.
• Modify existing test to verify non-string input parameter is working properly in framework='SCRIPT' pipeline.

[yoonspark]

Many of my comments are stylistic feedback, so I agree with Shardul that we can fast-track merging this to unblock other tickets necessary for the upcoming launch.

One overarching Q: Are there going to be only two flavors for the PythonOperator (i.e., per artifact and per session)? Is the new Airflow template general enough to accommodate any new flavor (if applicable)?

[mingjerli]

well .... I personally think there should be DockerOperator and KubernetesPodOperator; but I don't see we should worry the integration problem right now.