Overlay Quicktest Version 1

**PLEASE ONLY LOOK AT newquicktest.js, newquicktest.html, newquicktest.css, gruntfile.js, and list_of_quicktest.json**
**EVERYTHING ELSE ARE JUST ADDED QUICKTESTS FROM 2UP** 

**Steps to use**
0. There are already some pre-existing quicktests, but to add a new one, make a quicktest & drop it into appropriate category directory under quicktest/new/list
1. Run grunt
2. `grunt lq` to update list_of_quicktests.json
2. go to http://localhost:9999/quicktests/new/newquicktest.html
3. Select Category, enter branch, expand to set svg width and height, then run.

**Hotkeys:**
- key 1 -> only show plots rendered with 1st branch
- key 2 -> only show plots rendered with 2nd branch
- key 3 -> show all plots overlaying rendered with 2 versions of plottable
- key 4 -> hide all

**Notes:**
- I would like to make the `grunt lq` task run periodically (once everyday or so)
- All quicktests in my directory do not explicitly set height or width anymore, and I pass in the svg itself instead of a div to append. This is because I could not find a way to override the dimensions in any other way.
- Plans for Version 2 include a sidebar that has all quicktests with interface to 'tick off' active quicktest to "hide" them. This way, people can view a single quicktest, search quicktest by names, filter quicktests etc.
- For now, I will continue to slowly migrate our existing quicktests until version 2
- More comments the better. Thanks


after pressing 1
![screen shot 2014-10-30 at 5 14 56 pm](https://cloud.githubusercontent.com/assets/8551049/4854478/fc370f5c-6092-11e4-929c-ba684987b0e6.png)

after pressing 3
![screen shot 2014-10-30 at 5 15 19 pm](https://cloud.githubusercontent.com/assets/8551049/4854480/13033422-6093-11e4-954e-04bd8214d9bd.png)

expanding for svg dimension input fields
![screen shot 2014-10-30 at 5 16 34 pm](https://cloud.githubusercontent.com/assets/8551049/4854494/47c8d18a-6093-11e4-8e24-dabd36f00597.png)




I don't think you need to automate this process as long as we know how to do it.  It is at your will but if the work to automate is more ambiguous/annoying than just adding an input, I don't really see the point