It's assumed that when push is available, the pushHandler is used and data is saved in _PushStatus.
This allows Parse Dashboard push history to be enabled: ParsePlatform/parse-dashboard#378
* Break dependency on MongoCollection for updateMany
* Move transformWhere usage into MongoTransform
* Pass parse schema into transformUpdate
* break dependency on schemaController
* remove schema parameter
* move key name validation up one level
* Move validation out of mongo adapter
* Move validation into Parse Server and transformUpdate in Mongo Adapter
* Update mongo adapter
* Use adapter API
* use and fix mongo adapter api
* Remove/rename stuff
* Kill transform in DBController
* better imports for transform
* Tidy ConfigRouter
* Remove schemaController in more places
* Remove comment
* Move Parse Server logic into Parse Server and out of MongoAdapter
* Move untransforming up one level
* Make find() in MongoStorageAdapter
* Put nested object untransforming into it's own function
* Simplfy nested untransform
* Don't mess with inner object keys called _auth_data_*
* Prevent untransforming inner object keys named _p_*
* Fix inner keys named _rperm, _wperm
* Fix bugs with inner objects behaving strange when other fields have same name as key in specific circumstances
* remove params from untransform nested object
* Revert changes to find
* Cache users by objectID, and clear cache when updated via master key
* Go back to caching by session token. Clear out cache by querying _Session when user is modified with Master Key (ew, hopefully that can be improved later)
* Fix issue with user updates from different sessions causing stale reads
* Tests aren't transpiled...
* Still not transpiled
* Add MongoDB 3.2 to test matrix
- Updated mongodb-runner to support specifying storage engine
- Specifying mmapv1 explictly because of new 3.2 default
* Increase jasmine.DEFAULT_TIMEOUT_INTERVAL to 3 seconds
* Use fixed mongodb-runner
* Increase jasmine.DEFAULT_TIMEOUT_INTERVAL to 15 seconds
* Update to mongodb-runner 3.3.2 upon release
