Fix ASSERT_FALSE to preserve const-correct boolean evaluation

[Abhi10111]

Problem:
ASSERT_FALSE negates the expression before passing it to AssertionResult,
which forces early boolean conversion and bypasses the
AssertionResult(const T&) constructor. This leads to inconsistent overload
resolution compared to ASSERT_TRUE when types define both const and
non-const operator bool().

Solution:
Both ASSERT_TRUE and ASSERT_FALSE now pass the original expression to
AssertionResult, allowing const-correct evaluation. The expected boolean
value is compared after AssertionResult construction, restoring symmetric
behavior.

Tests:
Added a regression test demonstrating the inconsistency with a type that
defines both const and non-const operator bool(). The test fails on main
and passes with this change.

Fixes #4832