feat(protractor): implement reduce and filter for ElementArrayFinder

See https://github.com/angular/protractor/issues/877
fix(launcher): report summary when specs fail
feat(pause): allow the user to specify a port to be used for debugging

Using browser.pause(portNumber) will now start the debugger on the specified
port number.

Closes #956
docs(reference): clarify that cucumber is not as fully-supported as jasmine.

Note that cucumber is largely maintained by the community - the project
owners don't have the bandwidth to address every issue about it.
docs(configuration): fix documentation for onComplete

onComplete works for all frameworks and is not a subset of jasmindeNodeOpts.
Closes #921.
fix(protractor): allow exceptions from actions to be catchable

See https://github.com/angular/protractor/issues/959
chore(selenium): version bumps to selenium 2.42.2
feat(locators): implement by.options
feat(webdriver-manager): use proxy for webdriver-manager
fix(locators): findind elements by text should trim whitespace

WebDriver always trims whitespace from around the text of an element, so to be
consistent we should trim the text from button elements before doing
a by.buttonText.

Closes #903, Closes #904.
fix(protractor): removing a mock module that was never added now is a noop

It used to remove the last module - now is a noop.

Closes #764
chore(docs): update npmignore to ignore docgen folder
chore(minijasminenode): update to 1.0.0

minijasminenode@1.0.0 has no feature changes from minijasminenode@0.4.0.
fix(elementexplorer): element.all hangs in interactive mode
chore(release): version bump, changelog, and api for 1.0.0-rc1
feat(protractor): add iteration index to ElementArrayFinder.each
fix(mocha): mocha globals should be re-wrapped for every new suite

Closes #523, closes #962
feat(webdriver-manager): minor proxy enhancements

Added error handling for request - previously, any errors coming from
the request module were silently swallowed.

Fixed error handling to remove empty files when a download fails for
some reason.

Instead of throwing an error as an exception, the error is simply logged
and then the rest of the code continues. Previously, the uncaught
exceptions caused the program to stop immediately, without any chance of
recovering, or finishing other downloads. With the previous code, any
other downloads at the same time were interrupted, resulting in empty
files or incomplete downloads.

Logging the errors instead of throwing will allow the other downloads to
finish, and it will also allow removing empty files resulting from a
failed download, e.g. when no internet connection is available or with
an invalid proxy configuration.

Also evaluating both uppercase and lowercase proxy variables. Many tools
use proxy variables in the form https_proxy, others use HTTPS_PROXY. I
changed the code so both forms are evaluated. See the following links
for more info on this practice:

* http://serverfault.com/q/571887/140074
* https://wiki.archlinux.org/index.php/proxy_settings#Environment_variables
Fix a typo
docs(locators): clarify ng-repeat-start docs

Closes #1000