feat(gen): unify testing framework

Changes:
- add prompt for Jasmine or Mocha
- if Mocha choosen, prompt for Expect or Should
- use `<%= does() %>` to dynamically insert assertions (expect|should)
- add mocha variants for protractor tests
- add mocha options to protractor.conf
- remove `test/fixtures/(bower|package).json` from repo
- move runE2E functionality to runTest and simplify switch
- comment generator test functions
- use node `0.11.13` in travis due to issues with `0.11.14`+

Note:
Server-side jasmine test are needed to fully unify testing frameworks.
Once Jasmine tests are included for server, mocha dep can be removed
fully when selecting Jasmine.
Merge pull request #585 from kingcody/feature/unify-testing-frameworks

feat(gen): unify testing framework
docs(gen:endpoint): standardized comments
remove sauce connect addon from travis and replace with shell script
Merge pull request #599 from BenFradet/canary

docs(gen:endpoint): standardized comments
feat(app): add grunt jscs task for maintaining consistent code style
style(app): update style to match jscs style guide
fix(server): server should launch in dev mode if production env var is not specified

fixes #590
fix test framework options when scaffolding with existing project
add test for #403
test(gen): add tests for running the e2e tests in production mode
Merge branch 'fix-default-server' into canary
remove production e2e tests because issues with node 0.11.x
Merge remote-tracking branch 'upstream/canary' into canary

Conflicts:
	app/templates/_bower.json
	app/templates/server/config/environment/production.js
	test/fixtures/bower.json
	test/fixtures/package.json