feat(jasminewd): better error messaging when expect is called with a WebElement

Previously, using expect() with a web element would cause the webdriver
jasmine adapter to go into an infinite loop trying to resolve the promise,
since WebElement inherits from Promise but resolves to itself. Now
throws a more readable error.

Closes #178.
chore(testapp): cleaning up the test application

Remove the little used 'http' page, which was a leftover from the
angular http example.

Repurpose the 'repeater' page to hold all the repeater info.

Add a couple more tests for the global element variable, and remove
the backwards compatability suite.
chore(selenium): update to latest version

- Old .jar and chromedriver versions out of date.
- Chromedriver URL paths slightly changed as well.
- Paths found on this page: http://www.seleniumhq.org/download/

No known breaking changes.
chore(seleniumversion): update node selenium version dependency
docs(faq): add a faq on how to interact with browser javascript
docs(browser-setup): adding docs with information on how to configure browsers
docs(browser-setup): json notation is ugly, switch to javascript
(docs): Update readme.md

Updated readme with correct chromedriver links.
fix(debugging): switch debugging tests to the new test app urls.
fix(runner): exit with proper code when tests fail

When errors with messages matching /timeout/ were created, Protractor
clears the control flow so that the remainder of the tasks scheduled
for that spec don't bleed over into the next spec. This was messing up
the promises used in the runner, since they are also webdriver promises.
Long term, the runner should _not_ use webdriver promises. For now, fix by
having the runner resolve promises directly rather than through chaining,
and add a TODO to use promises which aren't connected to WebDriver's
control flow in the runner.

Closes #214.
fix(conf): fixing missing , in the reference configuration
Merge branch 'master' of https://github.com/angular/protractor