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
feat($parse): Custom private field tagging

Commit 3d6a89e introduced the concept of private fields that
can not be evaluated on an Angular expression.

This PR allows changing the matching pattern that tags a field
as private. It also allows disabling the private field access
restriction.

Some examples:
```js
myModule.config(function($parseProvider) {
  // disable private fields restriction
  $parseProvider.restrictFieldsMatching(null);
});
```

```js
myModule.config(function($parseProvider) {
  // Now private fields will be those whose identifier
  // begins with 'priv'
  $parseProvider.restrictFieldsMatching(/^priv/);
});
```

Custom private field identifiers allow backwards compatibility
with AngularJS <1.2 projects that use underscores in scope fields
(i.e. data retrieved from a MongoDB instance) while still
enjoying the new private field security policy.