Contacts mimeType should be specific to the action, not the included data

We incorrectly thought that the MIME Type used in the Contacts actions was
describing the data, but it is really supposed to describe the action.
So we renamed it from openpgp4fpr to encryptfileto in the gpg namespace

refs #1438
when calling gpg2 command-line-style, use "--trust-mode always"

We don't yet have any concept of trust management in the app yet, so set it
to "always" so we can actually encrypt to keys, etc.
move string to XML so it can be translated
handle "Encrypt File To" ContactIntent using the gpg2 command line

This is a first step to getting the full flow working. Right now, its using
the gpg2 tool in a Runtime.exec() call, then just writes out the file next
to the original file to be encrypted.  Ultimately, gpgcli should handle
incoming streams, EXTRA_TEXT, EXTRA_DATA, etc.

refs #1438
"Encrypt File To" sends encrypted file via SEND Intent, i.e. for email, etc

Use the incoming email address to generate an ACTION_SEND Intent, and popup
a chooser so that it is a seamless experience:

1) click "Encrypt File To"
2) select file
3) choose app to send the file with

closes #1438
also refresh key list view after receiving from keyserver, refs #1486
put all of the single line Activity declarations at top of AndroidManifest

Just trying to make them a bit easier to find.
include a set of public keys as a test file
add a script to set up the ant builds, following the Guardian standard
in GnuPG.gpg2(), run gpg2 in a shell and output stdout/stderr to logcat

Using NativeHelper.gpg2 in a CommandThread seems to trigger pinentry fine,
so I figured perhaps its related to running the command in /system/bin/sh.
This also dumps stdout/stderr to logcat so we're not flying blind.

refs #1560
rename MESSAGE_OKAY to MESSAGE_OK

This mirrors the Android style, e.g. RESULT_OK, etc.
split out EncryptFileActivity's process into separate methods

This makes the process a lot clearer, and makes it easier to share the
Handler and Messenger once the Fragment/AsyncTask for running GnuPG.gpg2()
is in place.
run gpg2 operations in a custom AsyncTask+Dialog fragment

GnuPG.gpg2() always needs to be run in a thread, otherwise it'll block
PinEntryActivity from starting up, if its needed.

fixes #1560
add option to sign when encrypting using EncryptFileTo

refs #1438
ImportFileActivity: split out actions from Handler into methods

Just to make things clearer, especially as this class is ported to use
the Gpg2TaskFragment.
convert ImportFileActivity to use Gpg2TaskFragment and its AsyncTask

GnuPG commands need to be run in an AsyncTask, otherwise they block
the PinEntryActivity from being launched.

closes #1560
CreateKeyActivity: fix bad path for exported secret key backup

refs #1460
CreateKeyActivity: do not upload to keyserver by default

Since it is hard to undo the upload, this should not be on by default.
CreateKeyActivity: create properly formatted params to fix gpgme key gen

The parameters in the "params" string need to be in a specific order,
otherwise the ken gen process fails. gpgme does not give very specific
error messages, but since the data format is almost the same as
`gpg2 --gen-key myparamsfile`, its easy to test the params file there.

refs #1460
CreateKeyActivity: put entire gen-key process in try/catch block for clarity

This also makes it easy to do things like getCanonicalPath() without
having to add another try/catch block.

refs #1460