adding "fuzzy" comparators for vector/matrix tests

The issue of why the values are off is open -- however the difference between expected and comparators is out to six places at least -- and probably more. This is likely just floating point nuttiness.
Revert "adding "fuzzy" comparators for vector/matrix tests"

This reverts commit 08ee007d2342428bf17d1a2abb4c795f23be0e83.
adding documentation, moving threshold arguments

also validating threshold as it is now a required argument
Updating packages to hopefully make Travis less unhappy
removing .11 from the stack; 0.11 is a developers release
Updated GA tracking with new ID

Had to create a new property for Github domain in Google Analytics.
updated leapjs README.md to include updated tracking pixel
being specific about arguments under test

making the matrix test specialized to 3 x 3 matrices.
Merge branch 'unit_test_fix' of github.com:leapmotion/leapjs into unit_test_fix
pulling assertUtil include out of tests
Validating common path as well.
Merge branch 'refs/heads/master' into unit_test_fix

Conflicts:
	test/frame.js
	test/hand.js
temporarily not running integration tests to locate failure scenario
did a lot of work to get phantom tests to pass
reverting module req's to master / previous version
fixed accidental s/r of test descriptions; style fix
changed arguments to OK for clarity
label fix
condensing old vector comparison; fixing label typo
Merge pull request #120 from leapmotion/unit_test_fix

Adding unit test library with vectorCloseTo and matrixCloseTo assertions.