Mock server returns incorrect entry set when filter contains (! (& (...))) or (! (| (...)))

[qha]

When computing elements of an "and" or "or" node evaluate_filter_node in the mock server handles the unmatched elements just like the matched elements.

What it really ought to do is to use:

• "or" logic for matched elements when handling unmatched "and" elements
• "and" logic for matched elements when handling unmatched "or" elements

This is where i found the issue (current latest commit on dev):

ldap3/ldap3/strategy/mockBase.py

Line 778 in 653340d

elif node.tag == AND: