Support Airflow 2.x operators (runtime specific components)

[lresende]

What changes were proposed in this pull request?

Support Airflow 2.x operators (runtime specific components)

Fixes #2124

After updating the elyra examples to have Airflow 2.x components, and register that in Elyra, I can see the airflow components and have the properties show up ok on the Pipeline Editor

Developer's Certificate of Origin 1.1

   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

[shalberd]

Yeah, there are still some changes necessary at airflow_component_parser, though, regarding the properties and values of each airflow operator.
Even though the GUI presence of the operators is ok, when assembling the DAG code from the values and defaults entered, e.g. from Bash operator, the assembled DAG is not correct.

#2124 (comment)

#3208 (comment)

Thank you though for making this starter-PR more complete in the other aspects here. I will see what I can find out about the inner workings of component_parser_airflow in conjunction with the new airflow operator classes, like None vs. Empty String for Bash operator cwd property (empty string is wrong ...) ... I just never had time yet to fully debug.

Last time I tested, for example the Bash operator cwd property in the assembled DAG code was made to be "" empty string, when in fact it should have been None if no value is specified in the GUI field.
https://github.com/apache/airflow/blob/2.10.4/airflow/operators/bash.py#L162

I am thinking: there is a test for the kfp component parser

https://github.com/elyra-ai/elyra/blob/main/elyra/tests/pipeline/kfp/test_kfp_component_parser.py

but not the airflow component parser ... so maybe it would be good starting a combination of a test for airflow component parser plus modifications to
https://github.com/elyra-ai/elyra/blob/main/elyra/pipeline/airflow/airflow_component_parser.py