fix: no longer hide exceptions when loading session file

[gigajuwels]

This PR will require that the session file can be de-serialized. If it can't be de-serialized, the entire Core init process should fail.

[skibitsky]

I agree that a deserialization failure should throw an exception here. However, I'm concerned about a situation where, if the session cache is already corrupted, the exception being thrown might prevent the core from initializing. In such a scenario, clients could get stuck, unable to reset the corrupted cache. They'd then have to initialize the proper storage separately and manually clear the cached session. Given this, perhaps we could catch the exception during Core initialization, log the error, delete the corrupted session, and then proceed with the Core initialization process?

[skibitsky]

Just realised that it didn't hide exception: bc8c1f1#diff-ba33f66e80b057d0ef22533f2a00a6c8c68ef5395435e206c3a4f6a9a35e17c3L123