fix(util): Reverse the order events are triggered

Reverse the order that an event is triggered so the autocomplete directive
can work correctly with Angular 1.5, since the order that child directives
are compiled has been changed in that version of the framework, due to lazy
transclusion (see angular/angular.js#13884 and
angular/angular.js@652b83e).

Closes #638

Author: mbenford

src/util.js

@@ -111,7 +111,7 @@ tagsInput.factory('tiUtil', function($timeout, $q) {
                     if (!events[name]) {
                         events[name] = [];
                     }
-                    events[name].push(handler);
+                    events[name].unshift(handler);
                 });
                 return this;
             },

test/util.spec.js

@@ -61,17 +61,17 @@ describe('tiUtil factory', function() {
 
         it('stops the propagation of an event', function() {
             // Arrange
-            var callback1 = jasmine.createSpy().and.returnValue(false),
-                callback2 = jasmine.createSpy();
+            var callback1 = jasmine.createSpy(),
+                callback2 = jasmine.createSpy().and.returnValue(false);
 
             // Act
             sut.on('foo', callback1);
             sut.on('foo', callback2);
             sut.trigger('foo', 'some data');
 
             // Assert
-            expect(callback1).toHaveBeenCalledWith('some data');
-            expect(callback2).not.toHaveBeenCalled();
+            expect(callback2).toHaveBeenCalledWith('some data');
+            expect(callback1).not.toHaveBeenCalled();
         });
 
         it('returns the object instance so calls can be chained', function() {