Don't crash due to old cached Settings objects

Settings doesn't need to wtf on bad input, it should be caught
upstream. (ideally all upstream cases catch exceptions, but
it's easier to just have the specific cache de-serialization
case look for Settings failures, as it does now for Account.)

Change-Id: I5fa6a3e3095c81598e75f684f96ccb99ed3bb8ff
2 files changed