- fixes #3017 and possibly #3084

Seems like @gero3 is MIA. We'll try again on the next cycle.

Ok, lets give this a push :) @gero3 webgl_lensflares.html seems to be broken.

make Matrix4.getPosition() deprecated and replace all usages in core library with Vector3.getPositionFromMatrix()

Renamed Vector3 projectPoint() to applyProjection() as per @WestLangley suggestion in bb873d16.

@WestLangley I've changed most of the vector.applyMatrix4() to vector.projectPoint().
Feel free to change back the ones that aren't needed (or let me know which ones can need to be changed back and I will do it).

Extra feature detection tests, to know what to load when using library

e.g. 
If no compressed texture support, load regular textures etc
If no float texture support, do multi pass rendering and pack float into rgba
If no dervitives do something else...

Removed Vector* add() to addVectors() and addSelf() to add(). Same with sub, cross, min, max, lerp... Renamed Matrix* and Quaternion multiply() to multiplyMatrices(), multiplyQuaternions() and multiplySelf() to multiply(). See #2860.
Good thing we have a ton of examples to make sure nothing is broken. The unit tests also helped. However, I suspect I've left something unchanged.

Frustum.contains -> intersectsObject, containsSphere->intersectsSphere, removed Frustum.containsAnyPoints, .transform.  Update unit tests accordingly.

Renamed .multiplyMatrix* to .applyMatrix* and .multiplyQuaternion to .applyQuaternion as suggested by @WestLangley in #2860.

Makes the code so much nicer imho...

Fixed inconsistent precision for lensflares and sprites shaders causing troubles on mobile (thanks to @phoboslab).

See #2769

Renamed .deallocate() to .dispose() as discussed in #2760 and fdb737d0.

Still unsure of whether to rename it to dispose instead.
I guess a problem of the world deallocate is that you're unsure wether it is dealocate or deallocate.

See #2624

This will need some more thought, before we didn't really do anything about BufferGeometry deallocation.

It's hard to test because, I think, chrome is now automatically deallocating stuff on it's own
@alteredq I've done a combined deallocateGeometry and some things here and there would need to be refactored but... what do you think?

For the moment just continuing with having both vertex and fragment shaders using the same precision (not to get uniforms precision mismatch, see #1602).

See #2769

Also not sending anymore to GPU directional and hemisphere lights with undefined direction (0,0,0). This is to prevent black pixels in OpenGL.

Fixes #2742

Added shadow map type definitions and replaced shadowMapSoft boolean on the renderer with shadowMapType. The default type is THREE.PCFShadowMap, which amounts to the previous default of shadowMapSoft = true. A new type, THREE.PCFSoftShadowMap will enable bilinear filtering of the shadow in the shader for smoother results.

Also now sharing numericalSort between particles and morphs.

Fixes #2710

See discussion in https://github.com/mrdoob/three.js/commit/d951fcbcfa8efa8b7cecc10075e5e78be4027bac

This happens when you use MeshFaceMaterial for a single material model (that's what was going on in Lucy example).

Alternatively, we could set face.materialIndex by default to 0 instead of "undefined". This kinda makes sense, just would need to be checked if it wouldn't break things.

This was causing a major headscratching in deferred rendering where I just couldn't get rid of data alpha seeping into color channels.

Watch out for unexpected changes. I believe NoBlending is correct for opaque pass, but there could be some demos that depend on incorrect behavior with NormalBlending (getting transparency without setting "material.transparent" flag).

Most likely troubles could come from using transparent PNGs without setting "material.transparent".