fix: Handle fatal db error on load_account

[rakita]

No description provided.

[github-actions]

Valgrind Results:

==3996== Cachegrind, a cache and branch-prediction profiler
==3996== Copyright (C) 2002-2017, and GNU GPL'd, by Nicholas Nethercote et al.
==3996== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info
==3996== Command: target/release/snailtracer
==3996== 
--3996-- warning: L3 cache found, using its data for the LL simulation.
Snailtracer Host+Interpreter benchmark (2.0s) ...            not enough samples
==3996== 
==3996== I   refs:      471,785,671
==3996== I1  misses:          5,855
==3996== LLi misses:          2,903
==3996== I1  miss rate:        0.00%
==3996== LLi miss rate:        0.00%
==3996== 
==3996== D   refs:      229,164,271  (152,345,982 rd   + 76,818,289 wr)
==3996== D1  misses:        350,584  (    210,292 rd   +    140,292 wr)
==3996== LLd misses:        137,579  (      4,055 rd   +    133,524 wr)
==3996== D1  miss rate:         0.2% (        0.1%     +        0.2%  )
==3996== LLd miss rate:         0.1% (        0.0%     +        0.2%  )
==3996== 
==3996== LL refs:           356,439  (    216,147 rd   +    140,292 wr)
==3996== LL misses:         140,482  (      6,958 rd   +    133,524 wr)
==3996== LL miss rate:          0.0% (        0.0%     +        0.2%  )