ResourceService practically requires an IntentId as a consumer

In aspect of method signatures, ResourceService seems to accept any implementation of ResouceConsumer as a consumer of resources. But actually, application's unique implementation can't be used because Kryo used in ResourceStore can't serialize them. Because of that, IntentId is currently the only possible implementation of ResourceConsumer. We need to allow applications to use its own ResouceConsumer implementation instead of IntentId.