fix(semantic): evaluate const !, &, |, ^ on bool operands - #10212

Summary

Adds support for evaluating bool bitwise operations (&, |, ^) at compile time in constant expressions. The not_fn handling is also refactored to sit alongside the new bitwise operations under a shared guard that ensures all arguments are valid boolean constants.

Type of change

Please check one:

• New feature

Why is this change needed?

Previously, constant expressions involving boolean bitwise operations (&, |, ^) were not evaluated at compile time, causing them to fail or be rejected in const contexts. Only ! (not), ==, and != were handled.

What was the behavior or documentation before?

Boolean bitwise operations such as true & false, true | false, and true ^ false could not be used in const declarations.

What is the behavior or documentation after?

const declarations can now use boolean bitwise operations. For example:

const AND: bool = true & false;
const OR: bool = true | false;
const XOR: bool = true ^ false;

These are correctly evaluated at compile time to false, true, and true respectively.

Related issue or discussion (if any)

Additional context

A new test test_const_bool_bitwise is added to const_test.cairo to verify the correct compile-time evaluation of all three boolean bitwise operations.