Evaluate canary-run condition in run-tests SelectiveChecks

[gopidesupavan]

This will help cases like when run-tests becomes false if it is canary-run .
Some times tests are getting skipped in canary run.

We have condition in jobs to trigger for run-tests, even thought this works but often some times run-tests becomes false when the last merge commit main has only some UI changes. then this causing skipping of canary run tests jobs. see below it has skipped most of the jobs. because the selective check here https://github.com/apache/airflow/actions/runs/12602875121/job/35126775759#step:8:217 triggered only the ui file changes

https://github.com/apache/airflow/actions/runs/12602875121/job/35126775759
https://github.com/apache/airflow/actions/runs/12602875121/job/35126775759#step:8:310

---

^ 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.

[potiuk]

I think it would be better to reevaluate 'run-tests' condition in this case in selective_checks and make sure it's never false in canary runs. This would be more natural, actually testable with unit tests and we would avoid the strange ternary

[gopidesupavan]

I think it would be better to reevaluate 'run-tests' condition in this case in selective_checks and make sure it's never false in canary runs. This would be more natural, actually testable with unit tests and we would avoid the strange ternary

Yeah make sense , i think i got it where its failing check, let me get updated changes..

[potiuk]

Yep. Precisely :)