Bump croniter from <1.1 to <1.2

[ashwin153]

This minor release makes cron validation stricter. https://pypi.org/project/croniter/1.1.0/#id1

Enforce validation for month=1. Before this release we used to support month=0 and it was silently glided to month=1 to support having both day in month in 4th field when it came to have 6fields cron forms (second repeat). It will now raises a CroniterBadDateError. See corpusops/croniter#6 [kiorky]

[uranusjr]

Maybe we should bump all the way to <2.0

[github-actions]

The PR most likely needs to run full matrix of tests because it modifies parts of the core of Airflow. However, committers might decide to merge it quickly and take the risk. If they don't merge it quickly - please rebase it to the latest main at your convenience, or amend the last commit of the PR, and push it with --force-with-lease.

[potiuk]

Maybe we should bump all the way to <2.0

Why don't we remove any upper limit ? This should be our default action. We should limit something only upper-bound only if we know it does not work. We cannot rely on SemVer and we have constraints that protect us.

I just added a commit to see if tests pass.

[potiuk]

Looks good. Merging :)