- Remove a few unnecessary dependencies
- Add some comments around usage of 'api'
- Mark some of the dependencies as 'api' if they're necessary for use of the module
I think this is just vestigial: as things developed, we expected to
use JNA directly. Now all such access is an implementation detail of
the Application Services delivery vehicle.
The Proguard rules have been pushed to the application-services
repository, where they belong.
For history sync, we'd like to use a separate connection, since internally
sync operation is blocking and potentially very long-running.
At the same time, we'd like to maintain a shared connection for general browser
tasks.
Using getDatabasePath doesn't work without extra work on older API versions.
That location doesn't exist, and it seems like we'd need to add a bit of code
to check for its presence, create it, etc., before we can rely on that location.
All of our other code which stores files just uses `filesDir`, and I don't see
a reason not to put `places.sqlite` into that location as well. There isn't much
value in that file living in a "databases" folder.
