chore(jqLite): remove leftover attachEvent/detachEvent from tests
fix($browser): account for IE deserializing history.state on each read

IE 10-11+ deserialize history.state on every read, causing simple comparisons
against history.state always return false. Account for that caching
`history.state` on every hashchange or popstate event.

Also:
1. Prevent firing onUrlChange callbacks twice if both popstate and hashchange
event were fired.
2. Fix the issue of routes sometimes not firing the URL change in all browsers.

Closes #9587
Fixes #9545
refactor($animate): use $animate.$$setClassImmediately to save code
refactor($animate): clean up core $animate code
docs($compile): tiny grammar correction

Closes #9590
refactor($browser): more test coverage around history.state manipulation

Check that pushState is not invoked if $browser.url() and $browser.state()
is passed to $browser.url setter.

Also, a minor refactor in $browser.url code and $browser specs.

Refs #9587
refactor(ngAnimate): remove unused function argument

Closes #9585
test(currencyFilter): fix disambiguous locator warning in e2e tests

The e2e tests for the `currencyFilter` issued the following warnings:
> warning: more than one element found for locator by.binding("amount | currency:"USD$"")
This commit removes the warnings by locating the elements by ID and not by
binding.

Closes #9593
docs(limitTo): fixed incorrect field type

There is no such thing as [type=integer] only number

Closes #9591
docs($httpBackend): add module declaration for best understanding

According with the Issue #9537. This module declaration in the test is very important. When I started to test in angular I copy and paste this code to see how it works, and I get this `module undefined error`, and just after read some blog posts I figure out that this line is essential for testing your module. So, for best understanding of begginers this can be very helpful.

Closes #9563
docs(ngIf): fixes font color change

The single quote causes the color of the font to change in the example, so I changed the text in the example to account for this.

Closes #9599
feat($animate): allow $animate to pass custom styles into animations

$animate now supports an optional parameter which provides CSS styling
which will be provided into the CSS-based animations as well as any
custom animation functions. Once the animation is complete then the
styles will be applied directly to the element. If no animation is
detected or the `ngAnimate` module is not active then the styles
will be applied immediately.

BREAKING CHANGE: staggering animations that use transitions will now
always block the transition from starting (via `transition: 0s none`)
up until the stagger step kicks in. The former behaviour was that the
block was removed as soon as the pending class was added. This fix
allows for styles to be applied in the pending class without causing
an animation to trigger prematurely.
feat($animate): introduce the $animate.animate() method
docs(directive): add an example showing `templateUrl` functions

Related to #2895
docs(changelog): add release notes for 1.3
chore(npm): update npm dependencies

Some of previous dependencies versions (e.g. Karma) didn't work with
Node 0.11.14, see:
https://github.com/karma-runner/karma/pull/1182

The only dependencies not updated in this commit are:

1. grunt-jscs-checker: its
rules have changed a lot so it will require more work to use the newer
version
2. gulp-jshint: the update breaks docs linting, it requires investigation

Closes #9571
fix($parse): support dirty-checking objects with null prototype

Objects created with `Object.create(null);` do not have a `valueOf` method unless
they supply one themselves. To accomodate these, Object.prototype.valueOf is
used when the type of the value is "object", and the `valueOf` property is not
a function (E.G. it's not in the object at all).

Closes #9568
WIP - feat(core): add methods `every()` and `some()` (similar to `forEach()`)

NOTICE: This is just a POC implementation to see if there is interest for the feature.
        There are many performance improvements to be made and tests to be written (and run).
Sometimes it is useful to be able to iterate over an array/object, but abort the operation as soon
as some condition is met. This commit adds two methods that provide this functionality:
1. some:  Test whether some element in the array/object passes the test implemented by the provided
          function.
2. every: Test whether every element in the array/object passes the test implemented by the provided
          function.

Closes #263