[AIRFLOW-5695] use RUNNING_DEPS to check run from UI

[pingzh]

Make sure you have checked all steps below.

Jira

• My PR addresses the following Airflow Jira issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"
  • https://issues.apache.org/jira/browse/AIRFLOW-5695
  • In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a Jira issue.
  • In case you are proposing a fundamental code change, you need to create an Airflow Improvement Proposal (AIP).
  • In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

Description

• Here are some details about my PR, including screenshots of any UI changes:

Users are not able to run a task in the tree view page when the task state is None so users tend to Ignore all Deps, which will result in the task is run by two workers and then one of the worker will kill the airflow run itself in the heartbeat, which is less ideal. We should allow users to run tasks with RUNNABLE_STATES via UI.

Tests

• My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

• My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":
  1. Subject is separated from body by a blank line
  2. Subject is limited to 50 characters (not including Jira issue reference)
  3. Subject does not end with a period
  4. Subject uses the imperative mood ("add", not "adding")
  5. Body wraps at 72 characters
  6. Body explains "what" and "why", not "how"

Documentation

• In case of new functionality, my PR adds documentation that describes how to use it.
  • All the public functions and the classes in the PR contain docstrings that explain what it does
  • If you implement backwards incompatible changes, please leave a note in the Updating.md so we can assign it to a appropriate release

@KevinYang21 @YingboWang @cong-zhu @saguziel

[KevinYang21]

So what's left are:

DagrunRunningDep
DagrunIdDep
DagUnpausedDep
ExecDateAfterStartDateDep

I'm +1 for using RUNNING_DEPS when trying to trigger from webserver. Don't think the deps in the gap is what people triggering task from UI want to care. In fact from the comment I think it is meant to use RUNNING_DEPS in webserver.