Fix warning in airflow tasks test command regarding absence of data_interval

[tirkarthi]

Fixes below warning in airflow tasks test command along with fixing test cases. Similar to PR #20781 and #20579

/home/karthikeyan/stuff/python/airflow/airflow/cli/commands/task_command.py:129 RemovedInAirflow3Warning: Calling `DAG.create_dagrun()` without an explicit data interval is deprecated

cc: @uranusjr

[uranusjr]

This would not always work since infer_automated_data_interval is only designed to provide backward compatibility for DAG runs that are created before the data interval concept was introduced, and a DAG using a custom timetable would not work correctly with this method. I think infer_manual_data_interval is probably a better choice; it is not technically correct (the call below created a scheduled run), but the exact value of the data interval does not actually matter much here anyway since the run is only supposed to be a stub.

[tirkarthi]

yes, since run_type is not passed here this just calls the same part as underlying code to have same behavior. It's infer_manual_data_interval in tests since they pass run_type as manual. The dagrun is also deleted in the end so I guess it's ok.

airflow/airflow/models/dag.py

Lines 2582 to 2585 in ea55626

	if run_type == DagRunType.MANUAL:
	data_interval = self.timetable.infer_manual_data_interval(run_after=logical_date)
	else:
	data_interval = self.infer_automated_data_interval(logical_date)

[uranusjr]

I took the liberty to change this myself.

[potiuk]

Conflicts needs resolving

[tirkarthi]

@potiuk Rebased with latest main branch and resolved conflicts.

[potiuk]

Well. Not really all fixed.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions.