setup-ant: use a CURDIR variable
include pin: Guardian Project RSA 1024-bit original signing key
include pin: Guardian Project RSA 4096-bit signing key
REBASE include pin: Guardian Project RSA 1024-bit original signing key
REBASE include pin: Guardian Project RSA 4096-bit signing key
include pin: Tor Project RSA 1024-bit signing key
make startActivity() handle both setPackage() and setClassName()

An Intent can be targeted using both setPackage() and setClassName().
setPackage() narrows down the possible recipients to a given packageName,
while setClassName() set the specific Activity in an app to send to. The
trust check is based on packageName since that is what the APK signature is
tied to.  So if getPackage() turns up nothing, then try getComponent(),
which fetches the CompenentName which is a representation of the thing that
was set using Intent.setClassName()
startActivity() comes from Context not Activity

Reflect this reality in TrustedIntents.startActivity()
make addTrustedSigner's argument a Class rather than ApkSignaturePin

There is no sense in anyone instantiating the class since it is in effect a
singleton, and the only instance methods are for validating that the
certificate matches the fingerprint.  Using a Class as an argument mirrors
the syntax of new Intent(Context context, Class cls).
ApkSignaturePin: remove useless and unused getSHA256Fingerprint argument

getFingerprint() accesses the instance variable directly for the data.
REBASE make startActivity() handle both setPackage() and setClassName()
isReceiverTrusted() and isIntentSane() check getComponent() for packageName

The packageName can be set with setPackage(), setClassName() or setClass().

* getPackage() returns what is set by setPackage()
* getComponent() returns what is set by setClassName() and setClass()
addTrustedSigner() returns whether add was successful or not

At the very least, this is useful in the tests.
test that addTrustedSigner() will not accept ApkSignaturePin.class
add methods to remove Trusted Signers test if ApkSignaturePins are trusted

Since TrustedIntents is a singleton, there needs to be a way to remove
items from the list of trusted pins.  Getting the instance will inherit any
pins that were set in the past by a given app.
tests: get TrustedIntents instance in setUp()

Most of the tests need an instance, and it should be cleared each time.
REBASE test that addTrustedSigner() will not accept ApkSignaturePin.class
REBASE isReceiverTrusted() and isIntentSane() check getComponent() for packageName