fix($compile): don't terminate compilation for regular transclusion directives

Previously we would stop the compilation for both regular and element
transclusion directives which was wrong. Only element transclusion directives
should be terminal.
fix($compile): fix (reverse) directive postLink fn execution order

previously the compile/link fns executed in this order controlled via priority:

- CompilePriorityHigh, CompilePriorityMedium, CompilePriorityLow
- PreLinkPriorityHigh, PreLinkPriorityMedium, PreLinkPriorityLow
- link children
- PostLinkPriorityHigh, PostLinkPriorityMedium, PostLinkPriorityLow

This was changed to:

- CompilePriorityHigh, CompilePriorityMedium, CompilePriorityLow
- PreLinkPriorityHigh, PreLinkPriorityMedium, PreLinkPriorityLow
- link children
- PostLinkPriorityLow, PostLinkPriorityMedium , PostLinkPriorityHigh

Using this order the child transclusion directive that gets replaced
onto the current element get executed correctly (see issue #3558),
and more generally, the order of execution of post linking function
makes more sense. The incorrect order was an oversight that has
gone unnoticed for many suns and moons.

(FYI: postLink functions are the default linking functions)

BREAKING CHANGE: the order of postLink fn is now mirror opposite of
the order in which corresponding preLinking and compile functions
execute.

Very few directives in practice rely on order of postLinking function
(unlike on the order of compile functions), so in the rare case
of this change affecting an existing directive, it might be necessary
to convert it to a preLinking function or give it negative priority
(look at the diff of this commit to see how an internal attribute
interpolation directive was adjusted).

Closes #3558
fix(routeProvider): parametrized routes do not match against locations that would not valorize each parameters.
chore(travis): temporarily disable Firefox

I can't get it allocated on SauceLabs and so this is failing all the builds, making our Travis build useless.

I contacted folks from SL. Once we figure it out, I will revert this change.
chore(docs): fix broken IE8 test due to sanitization bug
chore($parse): convert parser() and lex() to prototype-based code

This reduces memory consumption of parsed angular expressions and
speeds up parsing.

This JSPerf case demonstrates the performance boost:
http://jsperf.com/closure-vs-prototype-ngparser

Chrome: 1.5–2x boost
FF: slightly slower (I would love to know why)
IE: 4x boost

To be clear, this doesn't have any impact on runtime performance
of expressions as demostrated in this JSPerf:
http://jsperf.com/angular-parser-changes

Closes #3681
fix(ngResource): Remove request body from $delete

Prevent the  obj.$delete instance method from sending the resource as the request body.  This commit uses the existing hasBody boolean to only set httpConfig.data for methods which should have a request body.

Closes #4280
docs($resource): remove extra "to" from $resource docs

Closes #4287
docs(tutorial/step_07): fix module name

Closes #4283
docs(filter): add missing semi-colon

Closes #4273
docs(ngList): improve grammar and clarity
docs(a): change model.$save() into something less deceptive

Closes #4215
fix(rootScope): make stopPropagation only stop its own event

All sibling event handlers residing on the same scope to were stopped
if one of them called stopPropagation.

Closes #4204
docs(tutorial/step02): fix missing brace

Closes #4301
docs(ngValue): add docs for ngValue directive

Closes #4267
refactor($parse): only instantiate lex/parse once

Closes #4286
docs(ngModel): fix grammar and improve clarity

Closes #4291
style(angularSpec): add missing semicolon
style(injectorSpec): add semicolons & test helpers
style(select): fix semicolons and vars