Check SQLite3 WAL size before initialization

[PimSanders]

When trying to initialize the SQLite3 WAL class an EOFError is thrown if the WAL file exists, but is empty. This PR fixes the issue by verifying that the size of the WAL file is non zero.

Required for fox-it/dissect.target#1454.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.05%. Comparing base (33bc02a) to head (cfe07e6).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #14      +/-   ##
==========================================
+ Coverage   81.91%   82.05%   +0.13%     
==========================================
  Files          31       31              
  Lines        2334     2346      +12     
==========================================
+ Hits         1912     1925      +13     
+ Misses        422      421       -1     

Flag	Coverage Δ
unittests	82.05% <100.00%> (+0.13%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Schamper]

Looks good but I thought of a small other improvement:

Can you add a close method that closes any file handle we opened ourselves, in case we passed a Path? Don't close it if we received a file-like object.

And add a __enter__ (that just returns self) and __exit__ (that calls close()). Then we can use context managers in dissect.target.

[Schamper]

I've made some slight changes so we don't need the additional boolean attribute. Let me know what you think.

[PimSanders]

Thanks! That was the approach I wanted to take, but I couldn't figure out how to do it and opted for the boolean instead.