fix the negation evaluations in fake sql

[hedyyytang]

What's changed
Negate both results from the binary operation evaluation to ensure negation is correctly applied.

How negation works

Negated Property - indicates an expression needs to be negated,	NegatedInt - used in bitwise XOR operation
True	1
False	0

If a 1 needs to be negated, 1 ^ 1  = 0

If a 0 needs to be negated, 0 ^ 1 = 1

If 1 doesn’t need to be negated, 1 ^ 0  = 1

If 0 doesn’t need to be negated, 0 ^ 0  =  0

NOTE:
There is some parsing issue where when a single NOT statement is applied directly after WHERE clause, the negated property is not set correctly. Took a look but couldn't fix it in a short time so gonna leave it for now. We don't write NOT for a single statement anyways since we use != or NOT IN directly.

Example

Prior to the change, the following query will return the count 9, because NOT (powerups > :powerups) is always true, and the result doesn't filter out the character luigi, who has nes console and 5 powerups.

        // greater than
        $pdo = self::getConnectionToFullDB(false);
        $query = $pdo->prepare("SELECT COUNT(*) as 'count' FROM `video_game_characters` WHERE `console` = :console AND NOT (`powerups` > :powerups)");
        $query->bindValue(':console', 'nes');
        $query->bindValue(':powerups', 3);
        $query->execute();

        $query->fetchAll(\PDO::FETCH_ASSOC));

After the change, the count result is 8.

Tests
Added unit tests