click-service: remove clicks with libclick, properly across 2 registries
As it turns out, removing clicks from 2 registries at once when an app
comes from a read-only DB has a side
effect of hiding the app in both registries, which is confusing when
user tries to install app again via click-service (which installs into
@all
only).
So, be smarter on what registry to run removal on. This requires linking into libclick to inspect which registry (or registries) the package is insalled in. And since we need that, we might as well execute the package removal in the click-service itself.
Tests are updated to account for this.
Fixes: #21 (closed)