Add Next Run to UI

[bbovenzi]

Adds info on the next run from next_dagrun in the hoem page list of all dags and on the individual dag pages.

#17726

Unfortunately, next_dagrun only existed on DagModel and not Dag so I had to manually add it to every relevant endpoint in views.py. I also had to do some weird js logic to format the dates in line with the rest of the UI.

Also, I tried to update the copy on execution date. Open to suggestions. (Updating use of execution_date throughout the UI will be a different PR)

Closes #2460

---

^ 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.

[potiuk]

Thrlilled ! That's one of those great features that look like small ones but can totally change your experience.

[github-actions]

The PR is likely OK to be merged with just subset of tests for default Python and Database versions without running the full matrix of tests, because it does not modify the core of Airflow. If the committers decide that the full tests matrix is needed, they will add the label 'full tests needed'. Then you should rebase to the latest main or amend the last commit of the PR, and push it with --force-with-lease.

[uranusjr]

Since there are many execution_date usages to change, this will be done in a follow-up PR instead.

[ashb]

By making this a <time> element it will automatically get converted by the timezone selector (not to mention that just semantically this is a time 😁)

[bbovenzi]

Oh yes, I forgot that we select elements by <time> in datetime_utils.js. Fixed.

[uranusjr]

I just noticed something. We are using next_dagrun_create_after for Next Run, but is still using execution_date for Last Run. So for example_bash_operator (see screenshot in the top message), the runs are two hours apart even though the schedule is one hour. I think we should change Last Run to use start_date instead, does that sound righ @ashb?

[bbovenzi]

I updated Next Run to use the execution date to be consistent with Last Run. I also added a tooltip for the next run to show the create after and data interval. For Last Run, I decided to extend the use of the tiTooltip we use in the tree view. All of these dates will also update whenever the app's timezone changes.

[uranusjr]

Don’t really understand the js code, but the end result looks awesome

[uranusjr]

Hmm a lot of tests failing, many seem to be related to the new dag_model addition to templates.