docs(CHANGELOG): remove reverted commit from 1.2.26

See https://github.com/angular/angular.js/pull/9079#issuecomment-57954483
chore(docs): update to dgeni 0.4.1 and dgeni-packages 0.10.1

Adds a new processor to identify dangling links
chore(npm): publish artifacts to npm

Closes #2877
docs(guide/introduction): fix grammar style

Changed "you would currently have to write" to "you would otherwise have to write".

Seems to make more sense this way since "currently" presupposes that someone new
to Angular would be coming from a different paradigm, which they may or may not be.

Closes #9428
chore(docs): remove unused gruntUtils import from docs config

As of commit 11c5bb7, the gruntUtils import is no longer needed in the
gitData docs config service.

Closes #9446
docs($injector): $injector isn't a function

Closes #9448
docs(misc/faq): grammatical error fixes

Merci beaucoup

Closes #9451
Closes #9450
docs(ngIf): wrap ngIf in code tags

Closes #9435
docs(guide/introduction): guice has moved to github

Closes #9416
docs(ngBindHtml): explain that angular-sanitize.js is needed to depend on ngSanitize

Added comment. You need to include angular-sanitize.js otherwise you cant use ngSanitize!

Closes #9400
docs($injector): clean up docs for $injector#has

Fixup return type and param info.

Closes #9452
docs($injector): injectors aren't functions

Closes #9453
chore(publish.sh): fix url in script console output
docs(guide/index): fix broken link
refactor($http) Simplify code by removing workarounds for older versions of Internet Explorer

This removes a workaround for IE 8 and and error handling for IE6.

Closes #9300
refactor($http) Use onload/onerror/onabort instead of onreadystatechange

Closes #9329
chore(IE8): remove all special code for IE8

Remove all code that was IE8 specific

Closes #8837
fix($compile): Handle the removal of an interpolated attribute

Handle the removal of an interpolated attribute before the
attribute interpolating directive is linked

Closes #9236
Closes #9240
fix($animate): clear the GCS cache even when no animation is detected

$animate will cache subsequent calls to GCS in the event that the element
with the same CSS classes and the same parentNode is being animated. Once the
animation is started then $animate waits for one rAF before flushing the GCS
lookup cache. Prior to this fix, if GCS was unable to detect any transitions
or keyframes on the element then it would simply close the animation, but it
would not trigger the rAF code to flush the cache. This issue caused a bug
which made it difficult to detect why certain animations are not allowed to
fire if the element didn't contain any CSS-based animations beforehand.

Closes #8813
fix($animate): abort class-based animations if the element is removed during digest

Prior to this fix, if the element is removed before the digest kicks off then it leads
to an error when a class based animation is run. This fix ensures that the animation will
not run at all if the element does not have a parent element.

Closes #8796