Hard overwrite on conflict for query owners (re #283)

[washort]

This fixes #283 though I'd love to see a better way to handle an action in a toastr notification than setting a global function as callback.

[jezdez]

@washort So with the looming issue of staying close with upstream in terms of API usage I just looked again at the toastr calls there. There are no uses of HTML in toastr popups and I think that means we should stay away from that as well.

In stead I think we can safely use the window.confirm function instead as it's used in various places in the code.

And since our confirmation query only applies to query owners it's okay UX wise.

In other words, depending on $scope.isQueryOwner I think we should just conditionally call window.confirm or toastr.error.

[jezdez]

@washort Do you want me to take a stab at this? (I know you've spent lots of time on this already)

[washort]

Sure, if you don't mind having a look.

[jezdez]

@washort Okay, found an own AlertDialog thing actually, which is what is used in other places already that fits the bill better than window.confirm.

[washort]

r+, this is obviously a better solution

[jezdez]

This got merged upstream as well.