docs(guide/directives): improve links to isolate scope docs

Link "isolate scope" to "Directive Definition object" section

Closes #7484
chore(release): publish ngMessages to bower
fix($compile): pass transcludeFn down to nested transclude directives

If you have two directives that both expect to receive transcluded content
the outer directive works but the inner directive never receives a
transclusion function. This only failed if the first transclude directive
was not the first directive found in compilation.

Fixes #7240
Closes #7387
chore($compile): make webstorm's regexp parser happy

Minor change puts \- at end of character pattern

In CLASS_DIRECTIVE_REGEXP and COMMENT_DIRECTIVE_REGEXP, putting the \- character at
the end of the character patter speeds up many IDE parsers and alleviates some
errors in certain IDE's. (WebStorm 8)

Functionally absolutely equivalent. No test change needed.

Closes #7093

Conflicts:
	src/ng/compile.js
fix(ngClass): handle index changes when an item is unshifted

Closes #7256
docs(changelog): release notes for 1.3.0-beta.9 release-naming
test($compile): use `trim` helper
fix(ngModel): do not dirty the input on $commitViewValue if nothing was changed

Calling `$commitViewValue` was was dirtying the input, even if no update to the view
value was made.
For example, `updateOn` triggers and form submit may call `$commitViewValue` even
if the the view value had not changed.

Closes #7457
Closes #7495
docs(tutorial): fix link to bower in step 12

Muchas gracias! \o/

Closes #7507
docs(guide/$location) remove duplicate 'Crawling your app' section

The "Crawling your app" section was duplicated.
I just removed the duplication and moved the section to the 'Caveats' section.

Closes #7244
perf($interpolate): optimize value stringification

previously we stringified numbers via toJson which was expensive, I optimized
the code so that toJson is invoked only if really necessary

Closes #7501
docs(guide): correct order of directive arguments within the animations chapter

Closes #7482
chore(travis): use SauceConnect v4

See https://saucelabs.com/docs/connect
chore(travis): use latest selenium on SL
chore(travis/e2e): update Chrome to v34

See 28ef2637c111d2940d2062c3cc8be29e7984f35a
chore(travis/e2e): use Chrome on Mac

Because of this[1] issue, which is Linux specific, we see very frequent failures.

[1]: https://code.google.com/p/chromedriver/issues/detail?id=467
docs(tutorial): fixed path to controllersSpec.js file

☆.。.：*・゜☆ DOMO ARIGATO MR ROBOTO ☆.。.：*・゜☆

Closes #7504
revert: fix($compile): pass transcludeFn down to nested transclude directives

This reverts commit 113850602de2f8bc396df4ffd54bb0f1be565b17.

This change introduced regressions for several scenarios.

reduction: http://jsfiddle.net/5242N/4/
feat($interpolate): escaped interpolation expressions

This CL enables interpolation expressions to be escaped, by prefixing each character of their
start/end markers with a REVERSE SOLIDUS U+005C, and to render the escaped expression as a
regular interpolation expression.

Example:

`<span ng-init="foo='Hello'">{{foo}}, \\{\\{World!\\}\\}</span>` would be rendered as:
`<span ng-init="foo='Hello'">Hello, {{World!}}</span>`

This will also work with custom interpolation markers, for example:

     module.
       config(function($interpolateProvider) {
         $interpolateProvider.startSymbol('\\\\');
         $interpolateProvider.endSymbol('//');
       }).
       run(function($interpolate) {
         // Will alert with "hello\\bar//":
         alert($interpolate('\\\\foo//\\\\\\\\bar\\/\\/')({foo: "hello", bar: "world"}));
       });

This change effectively only changes the rendering of these escaped markers, because they are
not context-aware, and are incapable of preventing nested expressions within those escaped
markers from being evaluated.

Therefore, backends are encouraged to ensure that when escaping expressions for security
reasons, every single instance of a start or end marker have each of its characters prefixed
with a backslash (REVERSE SOLIDUS, U+005C)

Closes #5601
Closes #7517
docs($interpolate): replace `jerk` with something nicer/more neutral

I thought `jerk` illustrated the "defacing" factor nicely, but I suppose it's not very nice to have
in official documentation.