Added Changes for Custom Resolver Activity

In order to get a custom resolver activity working, we needed to allow
our application to be the resolver (CMResolver). Also added in extra
EventLogTag for when an intent cannot be resolved.

Change-Id: Iab3fc344b70a41e135eb295b542c0cbcf0d4d2ce

Add System Property for Resolver

In order to distribute the custom Resolver with capps, we need
a way of updating which resolver to use.  This property will do
the trick.

Change-Id: I2ba27324599df1f2bb0200b2172fd9421edf8279

Fixed Possible Resolver Infinite Loop

There was a possibility in the case where the ApplicationSuggestions
are being used and the Resolver isn't replaced that an infinite loop
of the resolver starting itself up and finishing its current instance
would happen.  This will fix this case by no returning the Resolver
in the query if we aren't currently using a Custom Resolver.

This means that any custom resolver used needs to handle the case where
it gets returned a reference to itself when there are no other activities
to handle the intent otherwise.

Change-Id: I559a188f5011445e4ba91738b30d7ed367398406

Fix FileManager Interaction

After much thought about this last night, I decided that we can't
handle making sure the situation in
http://developer.android.com/training/basics/intents/sending.html#StartActivity
can actually be handled without possibly making a bad experience in
other situations (such as FileManager doing its own resolving).

This will now only pop it up when we query a function which could
possibly return the resolver like how it was before  the previous change.

Change-Id: I2e458a80d3e3f7c358949c210b5372933910ac7a
Issue-Id: CYNGNOS-1152