InterpretationsFragment is unfinished.

[VladislavAlfredov]

I started working on the caching for the interpretations last night, expecting that the activities and fragments are finished and working. It turnes out that they are not.

1. The next page button is never shown.
2. The RESTGetInterpretations used to only get page 0, and the page size was a magic number in the code (5).
3. There is no reload button for the InterpretationsFragment.
4. The overall class strcuture seems to be somewhat different from the InboxFragment, untested and most likely never used.

Implementing caching for the interpretations would not be difficult if they were implemented themselves.
As you can see from last 3 commits ( 36de15e, 4301169 and 9172cc6), I have not only abstracted the caching lists in RESTSessionStorage, such that the task would be simply :

1. Implementing the wrapper functions in RESTSessionStorage in a similiar way to those for inboxFragment. Maybe one or two conditions for forcing refresh if one has commented on a interpretation.
2. Calling these wrappers from the code (which is unfinished).
   But I also started refactoring the InterpretationsFragment...

Unfortunately I will not be able to continue with the refactoring, as I have other tasks to do.
I will also not be implementing caching, since in order to test it I would have to finish the Interpretations -REST client classes (InterpretationsFragment, RESTGetInterpretations, RestGetPicture, InterpretationCommentActivity (haven't even looked at the last one yet)).

As such I leave this as "wontfix".
I have implemented the wrappers and added todo comments or code in most of the appropriate places for caching calls. (da55bd5)