Add evalFilterNot and evalFilterNotAsync

[CremboC]

A recent PR #1619 added evalFilter and evalFilterAsync, here I'm added their cousins evalFilterNot and evalFilterNotAsync.

This is an optimisations instead of doing something like

_.evalFilter(foo.map(!_))

we simply do the more obvious

_.evalFilterNot(foo)

Only issue I see is the name of evalFilterNotAsync being bad. But it's follows the same pattern so not sure what else to call it...

P.S. I am expecting the tests to fail on this first commit. Specifically hoping only one of them fails and I'll fix it once it does.

[mpilquist]

I recently noticed we don't have filterNot on Stream -- want to add that too?

[SystemFw]

I'm going to say it: I think both evalFilterNotAsync and evalFilterAsync are overly specific :)

[CremboC]

@SystemFw I don't need the Async myself, but since it's there, I added the Not version for symmetry 🤷‍♂

[SystemFw]

Yeah I would remove both honestly :P