Add API Support for Filtering DAGs by Timetable Type

[henry3260]

relate: #53738

---

^ 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 airflow-core/newsfragments.

[pierrejeambrun]

Up here, @uranusjr the PR was just merged. That's needed for https://github.com/apache/airflow/pull/58848

[uranusjr]

After the timetable change, each built-in timetable has two identities, one in SDK and one in Core. I think it’d be a good idea for built-in timetables’ type_name to simply be the class name instead of the full import path to avoid user confusion. Custom timetables should still use the full import path as in this PR.

[henry3260]

cc @potiuk

[potiuk]

cc @potiuk

Not sure why I am called but I agree with @uranusjr

[potiuk]

BTW. @henry3260 -> you have conflicts to solve. I don't think you can get too far in getting it merged, before you do :)

[uranusjr]

We should also add some test cases on the type_name property to ensure its logic between built-in and custom timetables.