docs(CHANGELOG): update changelog with 1.2.27
docs(ngModelController): update wordings, add more general info

The wordings in setDirty etc. were specific to inputs, but ngModelCtrl
is agnostic to this and the preferred term is 'control'. I also
added some more info about this to the description, and linked to
the example that now lives at the bottom of the page.
docs($httpProvider): add info about `defaults.cache`

Closes #10134
fix(input): call $setTouched in blur asynchronously if necessary

If the model is blurred during an apply it should trigger
$setTouched asynchronously.

Fixes #8762
Fixes #9808
Closes #10014
chore(scripts): publish 1.2.x releases to npm with correct tag
docs(ngAnimate): Fix typo

The ngAnimate makes reference to a function `$animateProvider.classNamePrefix`
that does not exist, the correct function is `$animateProvider.classNameFilter`

Closes #10142
chore(scripts): fix 1.2.x tag name
docs($http): describe how to remove a header on a per request basis

Closes #10144
style($http): make jscs happy
docs($filter): clarify what is a valid filter name

Also updates the CHANGELOG to add info about this breaking some
previous invalid uses of $filter

Closes #10054
Closes #10131
docs(ngShow/ngHide): add spaces to improve readability of CSS

Closes #10101
docs(ngBindHtml): fix awkward wording

Fixes #10097
Closes #10129
style(ngBind): remove trailing whitespace
docs(ngAnimate.$animate): fix classes during the various animation phases

Closes #10124
chore(i18n): update locale to CLDR v26
chore(favicon): provide retina friendly favicon

See https://github.com/angular/angularjs.org/pull/143
test($route): fix test names
fix($route): fix redirection with optional/eager params

Previously, when (automatically) redirecting from path that fetured a
trailing slash and optional or "eager" parameters, the resulting path
would (incorrectly) contain the special characters (`?`,`*`) along with
the parameter values.

Closes #9819

Closes #9827
feat(ngMaxlength): add support for disabling max length limit

Previously, setting the maxlength to a negative number, would make all
input values invalid (since their length should be less than maxlength,
which is impossible).
This commit changes the behaviour of maxlength/ngMaxlength, effectively
disabling the maxlength validation (always returning true) when maxlength
is set to a negative number. This is more inline to how the HTML5
`maxlength` attribute works (both in browsers and according to the spec:
http://dev.w3.org/html5/spec-preview/attributes-common-to-form-controls.html#attr-fe-maxlength).

Related to #9874
Closes #9995
fix(ngMaxlength): ignore maxlength when not set to a non-negative integer

This makes the behaviour of maxlength/ngMaxlength more inline with the
spec.

Closes #9874