chore(e2e): remove npm err output from e2e

[filipesilva]

Currently, ng e2e output npm script error information in addition to protractor output when tests fail, for instance:

(...)
1) angular2-cli-quickstart App should display message saying app works
  - Expected 'My First Angular 2 App' to equal 'angular2-cli-quickstart works!'.

Executed 1 of 1 spec (1 FAILED) in 1 sec.
[01:50:23] I/launcher - 0 instance(s) of WebDriver still running
[01:50:23] I/launcher - chrome #01 failed 1 test(s)
[01:50:23] I/launcher - overall: 1 failed spec(s)
[01:50:23] E/launcher - Process exited with error code 1

npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "e2e" "--" "config/protractor.conf.js"
npm ERR! node v4.2.1
npm ERR! npm  v2.14.7
npm ERR! code ELIFECYCLE
npm ERR! [email protected] e2e: `protractor "config/protractor.conf.js"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] e2e script 'protractor "config/protractor.conf.js"'.
npm ERR! This is most likely a problem with the angular2-cli-quickstart package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     protractor "config/protractor.conf.js"
npm ERR! You can get their info via:
npm ERR!     npm owner ls angular2-cli-quickstart
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     E:\dev\ideablade\testing\angular2-cli-quickstart\npm-debug.log

This PR removes that extra information and converts the command/task to Typescript.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}