Of course, not all devices support Bluetooth...

Hopefully this gives users a better understanding of whether their
messages and contacts are accessible than "Briar is running" and "Quit".

GroupActivity needs to receive a similar treatment.

We check for compatibility by specifying a schema version and minimum
schema version in the code, storing them in the DB, and checking whether
the DB is too old for the code or vice versa.

Dev task #52. Known but unverified identities are also supported, but
currently unused. These will be used in future for contacts who've been
introduced but not verified face to face.

If the schema of the database is incompatible with the schema expected
by the code, the database throws a DbSchemaException. LifecycleManager
indicates the error to BriarService, which uses HomeScreenActivity to
show a notification and quit the app.

Private messages are now the same as group messages, but groups can be
private or public. When a contact is added, a private group is created
and designated as the inbox for exchanging private messages with the
contact.

This allows quick access to any part of the app, including quitting (two
touches).

This makes the contact list behave how alpha testers expected: touching
a contact shows private messages exchanged with the contact.