`u32` operations' inputs are not range checked

~~`Process` [doesn't add range checks](https://github.com/0xMiden/miden-vm/blob/a2d1a0a85ffbf13da70641210a1518fb1597c65f/processor/src/operations/u32_ops.rs#L182-L204) to the `U32and` and `U32xor` operations. I'm not sure if there's a historical reason why this wasn't done, but from what I can tell, this is a bug.~~

`U32and` and `U32xor` are consistent with other u32 operations in that they don't range check their inputs (but guarantee that their output is a `u32` *if* their input is a u32). We should revisit this design choice for all `u32` operations.

The issue is about u32 operations in processor/src/operations/u32_ops.rs, specifically U32and and U32xor. First, examine the file to understand the current implementation and how other u32 operations handle range checking. Then, review the design choice for all u32 operations, considering the guarantee that output is a u32 only if input is a u32. Done looks like proposing or implementing consistent range checking across all relevant operations.

由索引模型根据 Issue 内容生成。