Change schedules default catchup window to 1 year

[dnr]

What changed?
Change default catchup window to 1 year (will only affect newly created schedules)

Why?
Better match user expectations: we shouldn't skip runs for short slowness/unavailability, other parts of temporal always attempt to catch up

How did you test it?

Potential risks

Is hotfix candidate?

[MichaelSnowden]

Can you describe exactly what this will do? If I create a schedule to run something at the highest frequency possible (maybe every minute I don't know), but I disable the schedule feature (not sure if / how this is possible), and then I forget about it, and then a year goes by and I turn on schedules again because I have a new use case, will that mean we will execute that old workflow thousands of times to catch up?

[MichaelSnowden]

Hmm, actually, it looks like this is the exact same behavior as Airflow (catchup by default, up to a year), so it makes sense that our users would expect it, even if it seems a bit dangerous.

[dnr]

If you disabled the schedule worker for a long time and had a running schedule then yes, it could try to start a large number of runs. Depending on the overlap policy, it would be either 1 (default "skip" policy) or max 1000 (sequentially) or max 1000 (in parallel). That's not a thing that anyone should do, though