chore(doc-gen): generate examples for each deployment, e.g. jquery

Update to the latest dgeni-packages, which supports multiple
deployment environments for the examples.

Add a jQuery deployment environment for the examples.

Currently, the target of the runnable example iframe always points
to the default deployment environment, not to the environment under
which the main app is running.

Closes #6361
docs(guide/location): fix url-based link to AUTO module

Closes #6381
docs(guide/scope): fix url-based links refs to AUTO module

Closes #6382
docs(guide/i18n): fix url-based links refs to AUTO module

Closes #6383
docs(ngMock.$interval): fix return description

Closes #6384
docs(guide/compiler): fix url-based links refs to AUTO module

Closes #6385
docs(guide/di): fix url-based links refs to AUTO module

Closes #6386
docs(tutorial/step_05): fix url-based links refs to AUTO module

Closes #6387
docs(tutorial/step_06): fix url-based links refs to AUTO module

Closes #6388
docs(tutorial/step_11): fix url-based links refs to AUTO module

Closes #6389
docs(guide/filter): fix input type in example

Closes #6366
docs(*): fix anchors for members in api docs
chore(examples): remove ancient examples from the tree

Let these poor scripts retire, goodness.

Closes #6398
Closes #3310
fix($http): send GET requests by default

Fixes #5985
Closes #6401
fix($http): do not add trailing question

Closes #6342
feat(ngHref): bind ng-href to xlink:href for SVGAElement

This change makes the ngHref directive useful for SVGAElements by having it bind
to the xlink:href attribute rather than the href attribute.

Closes #5904
fix($parse): reduce false-positives in isElement tests

There are always going to be false positives here, unfortunately. But
testing different properties will hopefully reduce the number of false
positives in a meaningful way, without harming performance too much.

Closes #4805
Closes #5675
fix(isElement): reduce false-positives in isElement tests

Complimentary change to match changed $parse behaviour.
fix(input): use ValidityState to determine validity

In browsers where HTML5 constraint validation is (partially) implemented, an invalid number
entered into an input[type=number] (for example) input element would be visible to the
script context as the empty string. When the required or ngRequired attributes are not used,
this results in the invalid state of the input being ignored and considered valid.

To address this, a validator which considers the state of the HTML5 ValidityState object is
used when available.

Closes #4293
Closes #2144
Closes #4857
Closes #5120
Closes #4945
Closes #5500
Closes #5944
fix($location): parse query string when path is empty in hashbang mode

Before this fix, search queries in hashbang mode were ignored if the hash was not present in the
url. This patch corrects this by ensuring that the search query is available to be parsed by
urlResolve when the hashbang is not present.

Closes #5964