fix(ngView): Add template to DOM before linking other directives

The template needs to be added to the DOM before
other directives at the same element as `ngView` are linked.

Related to #5247.
fix(ngInclude): Add template to DOM before linking other directives

The template needs to be added to the DOM before
other directives at the same element as `ngInclude` are linked.

Fixes #5247.
perf($injector): remove invoke optimization that doesn't work

Closes #5388
style($injector): remove ws
fix(closure): add missing FormController extern definitions

Closes #5303
perf: use call and === instead of apply and == in type check functions

Updates isDate et al to use call instead of apply and === instead of ==.
The change to call brings minor performance improvement and === is just
better practice than ==.
http://jsperf.com/call-vs-apply-tostring

Closes #5295
perf($resource): use shallow copy instead of angular.copy

Replace calls to angular.copy with calls to a new function, shallowClearAndCopy.
Add calls to copy for cache access in $http in order to prevent modification of cached data.
Results in a measurable improvement to the startup time of complex apps within Google.

Closes #5300
perf(a): do not link when href or name exists in template

Change the a directive to link and hookup a click event only when
there is no href or name in the template element.
In a large Google app, this results in about 800 fewer registrations,
saving a small but measurable amount of time and memory.

Closes #5362
perf(jqLite): implement and use the `empty` method in place of `html(‘’)`

jQuery's elem.html('') is way slower than elem.empty(). As clearing
element contents happens quite often in certain scenarios, switching
to using .empty() provides a significant performance boost when using
Angular with jQuery.

Closes #4457
docs(TRIAGING): add info about "needs: public api"
docs(CHANGELOG): add v1.2.5 changes
chore(release): cut 1.2.5 singularity-expansion release
chore(release): start 1.2.6 taco-salsafication iteration
chore(travis): force the latest version of selenium

This might solve some flakiness on SL. At least Santi said that ;-)
docs: use q-io instead of deprecated q-fs

This recursive process.nextTick error[1] was probably coming from q-fs,
which is not actively maintained. This updates to q-io/fs instead.


[1]: https://travis-ci.org/angular/angular.js/jobs/15391590
docs: fix a broken link
chore(build): automate cutting a release, publishing to bower and to code.angular.js
chore(build): set execute flag on scripts
chore(build): fixes to release.sh
chore(build): fix release.sh