fix(bootstrap-prettify): share $animate and $$postDigestQueue with demo apps

Although demo apps run in an isolated environment, we need to be able to tell them to disable
animations when we are running end-to-end tests.  By sharing the same instance of $animate
between the two environments we can disable animation across the board.

The $animate service uses the $$postDigestQueue to run animations.  The outer $animate
service uses the outer $$postDigestQueue and to queue up these animations.  This means that
when we run a digest inside the embedded scope, the animations are never performed - they
just sit in the outer scope's queue and are only run when a digest is run on the outer scope.
By sharing this queue across the two scopes the animations are performed correctly.
refactor($animate): speed up animationsDisabled check
fix($animate): don't force animations to be enabled

The way that enabling of animations was set up, made it impossible to inject a
module into the bootstrap to disable animations for things like end 2 end tests.
Now animations are temporarily blocked by setting the animation state to RUNNING
during bootstrap, which allows the developer to permanently disable at any point
by calling $animate.enabled(false).
fix(ngScenario): correctly disable animations for end 2 end tests
fix(ngClassSpec): clear animation enable fn from postDigestQueue
fix(animateSpec): run digest to enable animations before tests
chore(release): cut the v1.2.0 timely-delivery release
chore(release): update cdn version
docs(changelog): release notes for 1.2.0
docs(guide/migration): add migration guide
chore(docs): allow periods in doc shortNames
docs(guide/migration): fix link to #2500
docs(guide/migration): fix up internal links
chore(release): update version number for next round of development
chore(package.json): revert to marked@0.2.9 to fix CI builds

The marked npm library brought in a breaking change at 0.2.10.
This commit ensures that we get exactly the version we want.

Closes #4822
docs(guide/migration): fix internal link
docs($sce): ng-bind-html takes an expression `{{}}`
fix(angular-bootstrap): make IE8 happy
fix($resource): don't use $parse for @dotted.member

params and paramDefaults support looking up the parameter value from the
data object.  The syntax for that is `@nested.property.name`.
Currently, $resource uses $parse to do this.  This is too liberal
(you can use values like `@a=b` or `@a | filter` and have it work -
which doesn't really make sense).  It also puts up a dependency on
$parse which is has restrictions to secure expressions used in
templates.  The value here, though a string, is specified in Javascript
code and shouldn't have those restrictions.
fix(ngIf): don't create multiple elements when changing from a truthy to another thruthy value.

Fixes #4852.