Modernize sdk

[flovilmart]

• Removes ParsePromise
• Removes backbone style options
• Updates documentations.

[codecov]

Codecov Report

Merging #620 into master will increase coverage by 0.02%.
The diff coverage is 76.47%.

@@            Coverage Diff            @@
##           master    #620      +/-   ##
=========================================
+ Coverage   84.57%   84.6%   +0.02%     
=========================================
  Files          48      48              
  Lines        4039    3851     -188     
  Branches      911     871      -40     
=========================================
- Hits         3416    3258     -158     
+ Misses        623     593      -30

Impacted Files	Coverage Δ
src/ObjectStateMutations.js	100% <ø> (ø)	⬆️
src/FacebookUtils.js	5.55% <ø> (ø)	⬆️
src/ParseSchema.js	100% <ø> (ø)	⬆️
src/CoreManager.js	100% <ø> (ø)	⬆️
src/StorageController.browser.js	100% <ø> (ø)	⬆️
src/ParseSession.js	89.74% <0%> (ø)	⬆️
src/LiveQuerySubscription.js	50% <0%> (+4.54%)	⬆️
src/ParseGeoPoint.js	95.31% <0%> (+5.6%)	⬆️
src/ParseHooks.js	92.06% <0%> (ø)	⬆️
src/Push.js	100% <100%> (ø)	⬆️
... and 20 more

---

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 b762756...3c4efb9. Read the comment docs.

[dplewis]

Looks good, although I don’t know much about jest.runAllTicks(), flushingPromises(), setImmediate and the such

[flovilmart]

The problem was that some executions needed to wait till all current blocks pending in the promises should be run. That changes with using JS promises. The Parse Promises would run the continuation blocks immediately if possible. With JS, those blocks are enqueue, therefore, we needed a way to flush the current blocks :)

[dplewis]

Ah makes sense, I learned something new.

[flovilmart]

Had to learn it the hard way!