Persistent job queue, derivative of android-priority-jobqueue.

Silent no-op if some encryption keys have already been loaded? Seems like it should be a throw or loading the new keys. In fact, if we only expect to set the encryption keys once I don't fully get why this isn't part of the constructor.