Fix nearSphere queries when sorting by another key on Postgres

[jaypatel24]

Currently the Postgres adapter always adds a sort on a GeoPoint field if doing a nearSphere query, which isn't the expected behavior.

Previously the added test case was passing for Mongo but failing for Postgres, but now it passes for both.

[dplewis]

You can pass in a sorted parameter false.

parse-community/Parse-SDK-JS#582

query.withinKilometers('location', point, 4800.0, false);

[jaypatel24]

Ah... I need to investigate further but it seems like the PostgresStorageAdapter might be ignoring that parameter, since it always adds the sort? If that's true, should we update it to only add the sort if sorted=true?

However, looking at these tests, it doesn't seem like sorted=true sets any additional fields in the query:
https://github.com/mtrezza/Parse-SDK-JS/blob/c594faaca9a17dc82edf7adc255e1aab46568a17/src/__tests__/ParseQuery-test.js#L604

[dplewis]

https://github.com/parse-community/Parse-SDK-JS/blob/master/src/ParseQuery.js#L1304

We try to make Mongo and Postgres to have similar functionality.

https://docs.mongodb.com/manual/reference/operator/query/nearSphere/#sort-operation

If we merge your PR the following will happen.

Mongo will sort by default
Postgres will no longer sort by default

If sort is false, we use $centersphere which doesn't sort that way both db will have same functionality.

[jaypatel24]

That makes sense, I think we can close this!