Provider to client-side only for Fennec Integration

There is a new db abstraction layer to provide this. Content Providers are beneficial for  sharing databases between apps and for the async CursorAdapter interface. Neither are needed on the service side, but the latter is handy on the client side for UI purposes. The bigger problem would be that a content provider requires a manifest declaration, and must not conflict; the app is not designed such that multiple clients can access a common db. Installing both MozStumbler and Fennec with the same Provider causes runtime errors.

Also, fixed lint warning as I hit upon them. Hopefully if we keep at this we can get from dozens or so, to zero.