Fix generate-constraints job condition in canary run

[gopidesupavan]

One more interesting thing :).

generate-constraints job skipped when UI only changes, this fine for normal PR builds, but for canary run we should trigger this job, this skip causes further dependent jobs skipped :)

https://github.com/apache/airflow/actions/runs/12619970959/job/35165290069

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[jscheffl]

Good catch!
Our CI seems to be full of surprises the more you look into it :-D

[gopidesupavan]

Merging now, one test failed not related to this, it seems test related to auth manager. will look into separate.

[gopidesupavan]

Good catch! Our CI seems to be full of surprises the more you look into it :-D

Yeah good that the skipped jobs are visible in UI :)

[potiuk]

Good catch! Our CI seems to be full of surprises the more you look into it :-D

It is (or should be) very simple - we should strongly avoid complex conditions in the yaml files - and do all the logic calculation in selective_checks - they are unit testable and "python" :).