add dag parsed time in DAG view

[leehuwuj]

At our company, user have to change their dag definition in their own git repository which is going to be pulled by git-sync service into our Airflow instance. Users have to wait a moment then checking the DAG code to see is their updates are refreshed in Airflow.
It'd be easier if we show the last parsed time in DAG view that user can easily compare the parsed time with current time.

This update will add a new label called Parsed at next to the Next Run tooltip of the DAG UI.

---

^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an 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 a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[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

[bbovenzi]

Nice! I'm just not sure if that's the best place for that info. I think it may be better in the /detail page

[jedcunningham]

Turns out it's already on the details page. What about if we added it to /code?

[leehuwuj]

Turns out it's already on the details page. What about if we added it to /code?

Good idea @jedcunningham , It'll be more friendly with users who checking their updates in the code without look closer into their code.
Should I keep the label there then add a condition to show in /code page only or put it inside the dag_code block?
I'll keep commit if our decision is simple because i'm not a front-end developer myself.

[jedcunningham]

Lets put it in the page body instead, above the code block? That work for you @bbovenzi?

[bbovenzi]

Lets put it in the page body instead, above the code block? That work for you @bbovenzi?

Yeah, let's put it in code.html inbetween subtitle and code

[leehuwuj]

Yeah, let's put it in code.html inbetween subtitle and code

I'm a bit confused, I think it's dag_code.html and it seems that the code.html has not be used for a long time!

[bbovenzi]

Yeah, let's put it in code.html inbetween subtitle and code

I'm a bit confused, I think it's dag_code.html and it seems that the code.html has not be used for a long time!

Yes, my bad.

[leehuwuj]

Just moved to dag_code.html:

[boring-cyborg]

Awesome work, congrats on your first merged pull request!

[jedcunningham]

Thanks @leehuwuj! Congrats on your first commit 🎉