`.notEqualsTo` Parse.Query-function weirdness on postgres (for nested objects)

#6177 # Issue Description

.notEqualsTo Parse.Query-function not behaving correctly on postgres (for nested objects)

Steps to reproduce

        var q1 = new Parse.Query("MyClass").equalTo("state.status","open")
        var q2 = new Parse.Query("MyClass").equalTo("state.foo",6)
        await Parse.Query.and(q1,q2).find()

        => [s] // correct

just changing .equalTo to .notEqualTo does not seem to differ at all.

        var q1 = new Parse.Query("MyClass").equalTo("state.status","open")
+++     var q2 = new Parse.Query("MyClass").notEqualTo("state.foo",6)
        await Parse.Query.and(q1,q2).find()

?       => [s]       // should be []

another simplified version:

        await new Parse.Query("MyClass")
        .equalTo("state.status","open")
        .equalTo("state.foo",6).find()

        => [s]      

        await new Parse.Query("MyClass")
        .equalTo("state.status","open")
+++     .notEqualTo("state.foo",6).find()

?       => [s]       // should be []

Environment Setup

• parse-server version: 3.9.0
• Operating System: alpine linux 3
• Localhost or remote server? localhost
• Postgres version: 11.5
• Storage engine: Postgres

Start by reproducing the nested Parse.Query case against parse-server 3.9.0 with PostgreSQL 11.5, comparing equalTo and notEqualTo results. Trace how the query is translated for nested objects, then add a regression test; done means the notEqualTo query returns [] for the reported data while equalTo still returns the matching object.