Depends on D8618.
This changes the way we expect users to build partitioned schedules. It makes @daily_schedule and the like obsolete.
The aim is to eliminate PartitionSetDefinitions as free-standing objects. Instead, a job can have partitioned config, which means that each run of the job corresponds to a particular partition, and the config for the job is based on that partition.
This means that the set of partitions is supplied when building the job, not when building the schedule that targets the job. In English, one might say "I have a job where each run fills in a days' worth of data in my table. I have a schedule that triggers that job at 7 am to process the prior days' worth of data."