docs($exceptionHandler): add a note about cases when exceptions are not delegated to the

$exceptionHandler

Add a note in $exceptionHandler's documentation about cases when exceptions are not delegated to
the $exceptionHandler, because they are executed outside of the Angular context. Most notable such
cases being the DOM event listeners registered using jqLite's/jQuery's on/bind methods.

Closes #7909

Author: gkalpak

src/ng/exceptionHandler.js

@@ -27,6 +27,18 @@
  * This example will override the normal action of `$exceptionHandler`, to make angular
  * exceptions fail hard when they happen, instead of just logging to the console.
  *
+ * <hr />
+ * Note, that code executed outside of the Angular context does not delegate exceptions to the
+ * {@link ng.$exceptionHandler $exceptionHandler}. Some common such cases include functions invoked
+ * by third party libraries and callbacks associated with XHR, setTimeout/setInterval and browser
+ * DOM events (including callbacks registered using jqLite's/jQuery's `on`/`bind` methods).
+ * For some of those cases, Angular provides native wrappers that transparently manage the $digest
+ * cycle and delegate exceptions to the {@link ng.$exceptionHandler $exceptionHandler} (e.g.
+ * {@link ng.$http $http} for XHR, {@link ng.$timeout $timeout}/{@link ng.$interval $interval} for
+ * setTimeout/setInterval). For the rest, you can explicitly ensure that the code is excecuted
+ * inside of the Angular context, by wrapping it in
+ * {@link ng.$rootScope.Scope#$apply scope.$apply()}.
+ *
  * @param {Error} exception Exception associated with the error.
  * @param {string=} cause optional information about the context in which
  *       the error was thrown.