fix(connection): MongoDB not able to connect to secondary member

[arjun3396]

fix for : https://jira.mongodb.org/browse/NODE-2868
We had a issue with not being able to connect to secondary member of replica set so raised a bug with MongoDb and they released a update to the driver which fixed the bug. This PR updates the MongoDb driver in parse-server to v3.6.3 from v3.6.2 to fix the connection string issue.

[codecov]

Codecov Report

Merging #6994 (cddfaae) into master (dbf04f3) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #6994   +/-   ##
=======================================
  Coverage   93.82%   93.82%           
=======================================
  Files         169      169           
  Lines       12405    12405           
=======================================
  Hits        11639    11639           
  Misses        766      766           

Impacted Files	Coverage Δ
src/RestWrite.js	93.82% <0.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update dbf04f3...cddfaae. Read the comment docs.

[arjun3396]

Not sure why the build is failing, I did not do any breaking changes, Can you help in resolving this?

[mtrezza]

The failing test cases are related to readPreference. Looking at the driver changelog, there haven been two related changes:

• sets primary read preference for writes (ddcd03d)
• use options for readPreference in client (6acced0)

I assume that if you add a failing test case for the issue you experienced with driver 3.6.2, it will also give you a hint about why these other tests are failing for the updated driver 3.6.3.

[dplewis]

Closing via #7026