Improved UI rendering of templated dicts and lists

[mehmax]

UI displayed rendered template dicts and lists as a json.dump.
This will not add any line breaks.
Especially when handling templated files (e.g. sql) line breaks will make the display more beautiful.
UI will now render each key+value from dicts and each index+value from lists seperately as own lines.

Example

Dictionaries

Old

New

Lists

Old

New

Nested dicts/lists

Old

New

Mixed

Old

New

It is now also possible to specify a dictionary or list path in template_field_renderers.
e.g.
{'configurations.sql' : 'sql' }
or
{'configurations[0] : 'sql'}

even nested dict/list paths are possible

{'configurations[0].sql : 'sql'}

closes: #17032

---

^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contribution Guide (https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst)
Here are some useful points:

• Pay attention to the quality of your code (flake8, mypy and type annotations). Our pre-commits will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it’s a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[mehmax]

Changed this to a draft, because I noticed that this can be improve this a little, so that template_field_renderers defined in the operator will be applied as well.

[potiuk]

Changed this to a draft, because I noticed that this can be improve this a little, so that template_field_renderers defined in the operator will be applied as well.

Looks good already :) @nathadfield ? And yeah - automated template_field_renderers application is perfect.

[ashb]

Rather than .0 can we have the python convention of [0] please.

[mehmax]

Hi @nathadfield @potiuk I am quite new to contributing. Would you mind taking a look at this and give me some feedback? :)

My approach is a bit different to yours @nathadfield. I wanted to expand every dict / list by default. If list or dict item is listed in template_field_renderes it will applied as well.

Thank you guys!

[nathadfield]

@mehmax I am by no means a seasoned contributor either! I did try to accommodate the expanding and rendering of 'op_kwargs` in my PR #17321 which I don't know if you've looked at it.

We definitely have similar and overlapping interests here so I'd be keen to hear from others about what we've both done and how we can bring them together.

For example, I could scale back the scope of mine so that it only focuses on delivering dictionary path rendering to operators.

[mehmax]

Rather than .0 can we have the python convention of [0] please.

done!

[potiuk]

I guess we can close it as #17321 has been merged.