Just to explore whether this would really produce confusion for users... There already are a number of Schedule* classes.
- ScheduleIntervalSchema - SchedulerInfoSchema - SchedulerJob - SchedulerMetricsJob (excludes test classes) But there isn't already a Scheduler class. Moreover, I think it's fair to say that none of these classes is user-facing. So airflow users would not be confonted with a Schedule class alongside a Scheduler class. Though it's true there remains simply the concept of the airflow scheduler, and the associated CLI command. I think what's salient to me is the fact that Schedule is really the simplest and most accurate expression of what this object is. And using a different-but-closely-related word instead, just to stay away from `airflow scheduler`, to me seems like a bad trade off. I don't really like what I'm about to suggest (i.e. i like AbstractSchedule / CronSchedule better) but we could add *Dag* to the front of the work e.g. AbstractDagSchedule / CronDagSchedule etc which might make things easier to separate.
