check for browserify cli option

if --browserify is passed to drive, we need to handle our bundling and test driving to accomodate
find_requirements module

it's not pretty, but it parses all requirements in our jstests to send to browserify and also comes up with a nice namespace for them
pass tests to driver to build browserify bundle

hacking this out, just want to see how all of this will work together
include the find_requirements driver

we will use it to build our browserify bundle
save browserify bundle for later reference

save the generated browserify bundle on the driver object for injecting into our test runs
updated dependencies (browserify, concat-stream)
added dependencies (falafel, cssauron-falafel)
added route to deal with grabbing the browserify bundle
ugly continuation if we need to build browserify

this will change, this is only for testing
added dependency (through)
use the real pipe to concat-stream

once browserify is built, send to concat stream and save on driver object
fix browserify attachment to driver

using the wrong this like some kinda scrub
if using browserify, add bundle to list of loaded scripts instead of require

i think this is where this needs to happen, testing things out to find out for sure
pass browserify option to driver so it can handle requests

whenever we get new tests we need to rebuild the bundle on the driver
pass a flag to possibly transform filedata for browserify

this isnt ideal, but its workable for now until we can come up with an optimal strategy
move browserify to Client rather than Driver

makes more sense I think, that way we can use a spawned Driver as a dummy server and throw whatever kinds of tests we want to at it
gutting previous work to change strategy
move everything browserify-specific to client
rewrite tests to conform to browserify if necessary
Check CLI for browserify flag