Add JSDoc for all methods and bring documentation up to PhET standards

[samreid]

At today's developer meeting, we agreed it would be nice to have complete and correct JSDoc for all methods. @phetsims/martin volunteered to help out.

To discover the types for @param you may wish to put debugger statements and examine runtime types.

To discover whether each method is @public or @private you may wish to search for usages, examine context, or use debugger statements or use strategy like phetAllocation.js and:

      var stack;
      try { throw new Error(); }
      catch( e ) { stack = e.stack; }

to detect where methods are called from.

[veillette]

List of files to review.

• BinPacker.js
• Bounds2.js
• Bounds3.js
• Complex.js
• config.js
• ConvexHull2.js
• Dimension2.js
• dot.js
• EigenvalueDecomposition.js
• LinearFunction.js
• LUDecomposition.js
• main.js
• Matrix.js
• Matrix3.js
• Matrix4.js
• MatrixOps3.js
• Permutation.js
• Plane3.js
• QRDecomposition.js
• Quaternion.js
• Random.js
• Range.js
• Ray2.js
• Ray3.js
• Rectangle.js
• SingularValueDecomposition.js
• Sphere3.js
• Transform3.js
• Transform4.js
• Util.js
• Vector2.js
• Vector3.js
• Vector4.js

[jonathanolson]

Seems like this represents an extension of the work for #38, should that be closed?

[veillette]

This is an extension of #38. A lot of documentation was added for #38 but there are a few files that need more documentation. I should be able to figure out most of it by reading the code. If i'm unsure about a particular method, I'll create an issue and assign it to @jonathanolson .