docs(tutorial): add experiment showing reverse sort
docs(ngMock/$httpBackend): fix testing example

Closes #3075
docs(guide/e2e-testing): clarify description of input(name) selector

The description of the input selector made it seem that you were selecting
an input element based upon it's name attribute. In reality, you are
selecting an element by the string in the ng-model attribute.
docs(ngPluralize): improve wording
docs(ngBind): clarify some of the writing
chore(build): temporarily add more logging to debug flakiness on CI
fix(compiler): corrects component transclusion on compilation root.

Closes# 2155
style(ngRepeatSpec): fix up colons and iit
chore(build): change logging level for e2e tests to info
docs(misc/faq): remove obsolte t-shirt instructions
chore: remove jstd leftovers
chore: update karma to 0.9.4

And also add shared config to make karma configs a bit simpler.
chore: clean up angularFiles.js
chore: set up Sauce Labs with Travis

This should not affect the Jenkins build at all.

Now, the Travis build uses Chrome on Sauce Labs, which in theory gives us opportunity to use any
browser/platform that Sauce Labs offers.
test(docs): fix invalid paths
chore(gitignore): add .agignore

I use a .agignore file to skip the build directory and some other files
while searching using Ag (see
https://github.com/ggreer/the_silver_searcher).
test($compile): use FQDN for img[src]

img[src]="https://foo" has the unfortunate problem that the browser will
actually try retrieving the resource the non FQDN foo.  The local DNS
might suffix a domain to this, resolve it, and try to present a
certificate for the https request and prompt the user to pick a
certificate. This commit avoids that by making foo a FQDN.  Note that it
might be better to replace foo with example.com (ref
http://tools.ietf.org/html/rfc2606#section-3).
docs(Angular.js): explain that toJson strips $... properties

In Angular.toJson, any properties with a leading '$' character will be
stripped from the resulting string since angular uses this notation
internally for services.  There have been complaints of not knowing
about this functionality until it breaks within their code.
docs($cacheFactory): show that you can access existing caches
chore: add karma-script-launcher plugin

This plugin is shipped as a default one with Karma. It's specified as a peer dependency.

I assume, there's an old version of NPM on the CI server, which does not support peerDependencies and therefore it didn't get installed.

This will make the dependency explicit.