[llvm] [ValueTracking] Compute knownbits for `(and/or cond0, cond1)` on both sides of branch (PR #82818)

[via llvm-commits]

goldsteinn wrote:

> You'll also have to adjust the logic in DomCondCache to recurse into all and/or, not just ones that match the top-level type. Unless you intentionally only want to handle the inverted type at the top level?
> 
> Please recheck compile-time impact after doing that.

https://llvm-compile-time-tracker.com/compare.php?from=55bc0488af077acb47be70542718d1bc17f3de4f&to=d3e117a04afb14a00686eb689213776b2921154b&stat=instructions%3Au

Mostly minimal with two notable regressions:
Stage2-O0-g: tramp3d-v4	20259M	20310M (+0.25%)
Stage1-ReleaseLTO-g: consumer-typeset	58135M	58200M (+0.11%)

https://github.com/llvm/llvm-project/pull/82818