Fix behaviour when invoked through deep links.

[Exulansis]

Describe the bug
If the wallet is invoked by some external application via a deep link, it does not always return control to the calling application. This depends on the callback specified in the callbackURL field of the interaction token.

To Reproduce
Steps to reproduce the behavior:

1. Pass a deep link to the wallet with an interaction token and an http callbackURL (e.g. https://myservice.com/authentication)
2. Go to the consent flow on the wallet
3. Observe that after the response is sent, the wallet remains open.

Expected behavior
The wallet should invoke the initial calling application, regardless of the callbackURL

[saifahn]

Duplicate of #1223? Or at least related, we should consolidate it into one issue?

[Exulansis]

Definitely related. We could set a tag / milestone for deep linking improvements. Although this one certainly holds priority.

[mnzaki]

@Exulansis is this still an issue?

[Exulansis]

It's no longer relevant. Can be closed.