Feature/mongo 2.6.5 jshint tests

Fix JSHint issues with new pipeline test code that was (mostly) ported from the original 2.6.5 mongo code.
Part of an effort to cleanup various JSHint issues in one fell swoop so that we can keep things a bit cleaner going forward.

Maybe. Personally I'd opt for creating an `Object` and using `JSON.stringify` if I needed the string version because you'd get better support from your tools.
Since I didn't know the context and this was a brute force effort to make things compliant I figured it'd be okay. There were only a couple of instances of things like this in the entire codebase anyhow. I'm sure we'll continue to improve these kinds of things as we go.