Easy to get into confusing situations when multiple schedules in the same repo have the same name

[sryza]

Received the following feedback from a user:

Hello! I've noticed that having multiple schedules (with the same name and different cron_schedules) attached to the same job doesn't raise an error and results to multiple schedules (with the same name and same cron_schedule).

first_schedule = ScheduleDefinition(
    job=my_job,
    cron_schedule="0 0 * * 0",
)

second_schedule = ScheduleDefinition(
    job=my_job,
    cron_schedule="1 1 * * 1",
)

kinda easy to miss this one cos the schedule name defaults to job + _schedule :smile: maybe it'll be better if an error or warning is raised to avoid unintended runs?

[yuhan]

A warning might make more sense cos I could see one actually wants to set up multiple schedules for the same job (e.g. two teams in the same org reuse the same job but will be monitoring different schedules on their own)