Redirect bitwise ops to logical ops in case the arguments are bool.

[mcourteaux]

This fixes an explicit type error on the WebGPU backend, where WGSL is not allowing bool ^ bool. Fixes #8596.

[abadams]

Failures unrelated. This makes sense, but this seems bordering on a language semantics change, and raises the oddity of having a bitwise_and intrinsic that's distinct from the And node even though they're identical for bools. I want to make sure we discuss this briefly in a dev meeting just to get a sanity check from others.

[mcourteaux]

I think the main argument is that Halide doesn't have a boolean type, and instead relies on uint1. So really we cannot make the distinction between a 1-bit int, and a boolean. So either we remove all logical operators (and say everything is an int, and therefore there are no logical operators to be defined on ints). Or we make the bitwise operators on uint1 redirect to logical operators.

Also note that the Python bindings do not even expose the logical AND operator (because python does not allow to override it), and instead relies on the users to use bitwise-AND & and bitwise-OR |.