docs($sce): fix code samples and example

The code samples were using `<pre>` tags rather than code fences (```) so they were
not being displayed correctly.

The inline code example (defined by a `<example>` element) had been placed in an
`@example` jsdoc tag, so rather than appearing inline at the declaration point in
the text, they were being appended to the end of the document in the `Example` section.

Closes #8053
docs($logProvider): debugEnabled is a method not a property

Closes #7824
docs($compile): fix minor typo

Closes #8048
docs(guide/di): clarify what "services" can be injected into .config() and .run()

Closes #8106
docs(guide/di): further clarification of what can be injected
docs(guide/controller): only show best practice controller creation

If it is not recommended to use a global function to create controllers,
why should it be shown as possible in the documentation?

One of the most common complaints about AngularJS is that it doesn't enforce
any convention. This is intentional and I generally like this.
However if we can avoid outright bad implementations in examples I believe
we should.

Closes #8011
docs(guide/controller): tweak initial example
docs(tutorial/step-7): improve injector information

I attempted to tighten up the language around the DI overview so that it was clearer
and more explicit. The sole responsibilities sentence was semantically jarring and
I think looks better as a list.  Some minor grammar improvements.

Closes #7099
docs(tutorial/step-0): remove hyphen and clarify items

Closes #5953
chore(docs/css): add margin between ul and p elements

Bootstrap CSS was removing the margin after ul elements if they were
descendents of other ul elements. But if the ul was followed by a p
then this looked terrible.

Related to #5953
docs($httpProvider): add missing documentation

Add documentation for $httpProvider default values

Closes #7782
docs($httpProvider): revert removal of comments

Related to #7782
fix(ngModel): test & update correct model when running $validate

If `$validate` is invoked when the model is already invalid, `$validate`
should pass `$$invalidModelValue` to the validators, not `$modelValue`.

Moreover, if `$validate` is invoked and it is found that the invalid model
has become valid, this previously invalid model should be assigned to
`$modelValue`.

Lastly, if `$validate` is invoked and it is found that the model has
become invalid, the previously valid model should be assigned to
`$$invalidModelValue`.

Closes #7836
Closes #7837
test(input): simplified $apply syntax
docs(error/$rootScope/inprog): fix $timeout typo

Closes #8071
fix(parseKeyValue): ignore properties in prototype chain.

Previously, properties (typically functions) in the prototype chain (Object.prototype) would shadow
query parameters, and cause them to be serialized incorrectly.

This CL guards against this by using hasOwnProperty() to ensure that only own properties are a concern.

Closes #8070
Fixes #8068
docs(tutorial/step-9): link to list of filters rather than filterProvider

Closes #8082
fix(input): modify email validation regexp to match rfc1035

Previously, domain parts which began with or ended with a dash, would be accepted as valid. This CL matches Angular's email validation with that of Chromium and Firefox.

Closes #6026
chore(tests): increase timeout for navigation in ng-href tests to avoid timeouts

Previously, the timeout for ng-href tests waiting for the url change after a link
was clicked was only 1000 ms. This was causing some flaky timeouts, so increasing
the wait to 5000 ms.
fix(input): escape forward slash in email regexp

This messed up with syntax coloring and variable hovering in chrome developer tools and made debugging really difficult.

Closes #8096