queryFilter boolean handling is inconsistent between JDBC and DS repositories

When performing a queryFilter against IDM with a JDBC repository with a negated value, e.g. "!{attribute eq true)", the results returned differ when compared to a DS repository.

To re-produce, create three managed objects with a searchable boolean attribute:

1 true
1 false
1 undefined

When using _queryFilter=test eq true, the first user (true) is returned
When using _queryFilter=test eq false, the second user (false) is returned
When using _queryFilter=!(test eq true), the behaviour changes depending on if we use a JDBC or DS repo.

For DS, the false and undefined user are returned
For JDBC, only the false user is returned