Prep for 2.0.5 development.
fix creation of RevoluteConstraint by passing maxForce in the options
Merge pull request #783 from woutercommandeur/dev

fix creation of RevoluteConstraint by passing maxForce in the options
ScaleManager seeds _check private var with null to avoid later comparison check (thanks @jflowers45, fix #782)
P2.Body.applyForce should have used pxmi instead of pxm (thanks @Trufi, fix #776)
P2 fixed creation of RevoluteConstraint by passing maxForce in the options (thanks @woutercommandeur, fix #783)
Tilemap.getTile and getTileXY used to return `null` in 2.0.3 but returned a Tile object in 2.0.4 (with an index of -1), they now return `null` again.
Patching back into 2.0.4 master release a couple of important updates.
Merge branch 'origin/master'
2.0.5-dev build release.
Fix pointOnLine
Corrected algorithm via: http://stackoverflow.com/questions/11907947/how-to-check-if-a-point-lays-on-a-line-between-2-provided-points
Merge pull request #784 from woutercommandeur/dev

Fix pointOnLine
Line.pointOnLine corrected algorithm (thanks @woutercommandeur, fix #784)
Update TypeScript definitions

Made the "index" parameter optional to reflect the JS version.
The P2 DistanceConstraint method signature has changed. Updated Phaser so maxForce is now passed as object (fix #788)
Documentation updates.
Added an additional tile index check to P2.World.convertTilemap.
Moved the this._reversed flag outside of the property loop in Tween (as per tween.js issue 115)
Emitter.makeParticles updated to use Array.isArray() check on the key/frame values, so non-string objects can be passed in (thanks @AnderbergE, fix #786)
Doc updates.
Fix Phaser.Line.intersectsPoints by properly checking the boundaries
Tilemap.createFromObjects will now force the creation of the property again even if it doesn't exist (regression fix from 2.0.4)