Refactor tests / port to tape

[springmeyer]

While debugging #300 I suspected that the mocha tests might be behaving unpredictably. I wondered if porting to tape would resolve the issues in #300. They did not, but moving to tape seems ideal anyway (given https://macwright.org/2014/03/11/tape-is-cool.html). so I forged ahead on these.

Also solved in this PR along the way:

• Solves one part of Simplify logic around abi crosswalk #276:
  • Because After the nodejs series started releasing 2.x and above we've seen the ABI only get bumped with new major versions, predictably. we now assume the ABI even when the exact minor.patch version is not stored in the abi crosswalk. This will avoid it needing to be updated as frequently (only for new major versions).
• Applied better workaround in the appveyor.yml for node-pre-gyp Appveyor build failing for Windows x86 using Node 4.4.3 #209
• Started returning a non-zero error code with invalid usage (and added test for this).
• Solves node-pre-gyp broken on node v8 / windows #302 and Arguments like --dist-url/--nodedir not respected with npm 3.10.10 #300 by downgrading npm to avoid npm bugs

[isaacs]

Unless you're planning on running tests in the browser (which node-pre-gyp probably isn't going to do), node-tap might be a better fit. Then you get the runner, reporter, coverage, and test framework all in one.

[ajmas]

Any status update?

[springmeyer]

Going to stick with tape for the moment. I'm short on time and it was not immediately obvious to me how to port

node-pre-gyp/test/build.test.js

Lines 37 to 44 in 07704da

	test.Test.prototype.stringContains = function(actual, contents, message) {
	this._assert(actual.indexOf(contents) > -1, {
	message: message || 'should contain '+contents,
	operator: 'stringContains',
	actual: actual,
	expected: contents
	});
	};

over.