`<build>no` conditionals evaluation short circuiting

[Kojoley]

Fixes #162

[grisumbras]

Maybe it's better to change evaluate-conditionals-in-context to actually stop evaluation once <build>no is encountered?

[grafikrobot]

Maybe it's better to change evaluate-conditionals-in-context to actually stop evaluation once <build>no is encountered?

@grisumbras Ah, isn't that what the PR is already doing?

[grisumbras]

I thought it didn't, but now I see that return does actually return from a rule. I am pretty sure this was not the case. When was that changed?

[grafikrobot]

@grisumbras It was done long ago enough that I don't remember :-) Definitely before the 4.0 series of b2.

[grafikrobot]

/backport

[github-actions[bot]]

Successfully created backport PR for version/4.10.0:

• 261