chore(dump): fix our karma.dump bridge

previously it didn't work for dumping multiple objects

src/ng/rootScope.js

@@ -577,7 +577,7 @@ function $RootScopeProvider(){
        *
        * @description
        * Broadcasted when a scope and its children are being destroyed.
-       * 
+       *
        * Note that, in AngularJS, there is also a `$destroy` jQuery event, which can be used to
        * clean up DOM bindings before an element is removed from the DOM.
        */
@@ -601,7 +601,7 @@ function $RootScopeProvider(){
        * Just before a scope is destroyed a `$destroy` event is broadcasted on this scope.
        * Application code can register a `$destroy` event handler that will give it chance to
        * perform any necessary cleanup.
-       * 
+       *
        * Note that, in AngularJS, there is also a `$destroy` jQuery event, which can be used to
        * clean up DOM bindings before an element is removed from the DOM.
        */

src/ngMock/angular-mocks.js

@@ -787,6 +787,7 @@ angular.mock.dump = function(object) {
       } else if (object instanceof Error) {
         out = object.stack || ('' + object.name + ': ' + object.message);
       } else {
+        // TODO(i): this prevents methods to be logged, we should have a better way to serialize objects
         out = angular.toJson(object, true);
       }
     } else {

test/testabilityPatch.js

@@ -291,5 +291,7 @@ function trace(name) {
 
 var karmaDump = dump;
 window.dump = function () {
-  karmaDump(angular.mock.dump.apply(undefined, arguments));
+  karmaDump.apply(undefined, map(arguments, function(arg) {
+    return angular.mock.dump(arg);
+  }));
 };