Add operator or API run_type's to dag runs

[bbovenzi]

Description

Any dag runs created by the REST API or trigger dag operator will appear as a manual dag run. That can be confusing. Instead we could add two new run_types for API triggered Operator triggered. Open to better names.

For the API, a user should also be allowed to specify the run_type because sometimes it still is a manual button to click.

We may need to add checks to make sure it is a valid run_type.

Use case/motivation

No response

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[pankajastro]

for trigger by an operator like TriggerDagRunOperator may make sense to have a different run_type or maybe should inherit the run type of TriggerDagRunOperator operator for example if TriggerDagRunOperator runs for schedule run_type then the corresponding dag should have run_type schedule. But for triggering by API or CLI I feel is equivalent to manual trigger for airflow

[rohan472000]

@bbovenzi , suggestion about having a different run type for operators like TriggerDagRunOperator, it can be a valid approach to define a separate run type or inherit the run type from the triggering operator. However, by default, triggering a DAG run via API or CLI is considered as a manual trigger in Airflow.

[pedro-cf]

I believe it is important to distinguish:

• Webserver UI triggers
• Rest API triggers
• Operator triggers

[eladkal]

@bbovenzi given #61833 I think we have everything we need?