Add a more descriptive error message for messed up cache file error

Addresses this ticket: http://manage.dimagi.com/default.asp?131898

Gives a cleaner error message to the user:

    "Unfortunately an error has occurred on the server and your form cannot be saved.
    Please take note of the questions you have filled out so far, then refresh this page and enter them again.
    If this problem persists, please report an issue."

Note that we don't expect this error to happen very frequently at all.
this seems oddly coupled. could we instead create a base exception class for anything we can anticipate, and then catch that in the view and return something structured that would allow this to happen in a generic way? (feel free to make me elaborate on that if it's not clear what i'm suggesting)