UI-Router detection

[skelet00r]

I was running into an odd timing issue when using the closeByNavigation option alongside angular-ui-router package.

Reproduce:

1. navigate to route with resolve and an ngdialog that loads as soon as the controller loads
2. press back on the browser
3. navigate to the same route again

Problem:
The second time that you entered the route the $locationChangeSuccess would fire after the controller loads which then forces the dialog to close.

Solution:
Added detection into ngdialog for $stateChangeSuccess as that fires consistently with controller instantiation through resolves.

Demo
Current ngDialog
http://s.codepen.io/jdelibas/debug/KpeXmr

PR #227 ngDialog
http://s.codepen.io/jdelibas/debug/aOKLyO

[egor-smirnov]

Perfect! Thank you, merging.