fix(libs/pidstore): Detect corruption on startup and reset pidstore

[renaynay]

The recovery of an existing pidstore is not critical to node functionality and should not block the node's start-up if it was corrupted during an ungraceful shutdown. If corruption is detected, a fresh pidstore can be instantiated and used by the node.

Found by conduit.

[codecov-commenter]

Codecov Report

Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (65c6b65) 51.08% compared to head (0bb4fc0) 51.47%.
Report is 3 commits behind head on main.

Files	Patch %	Lines
libs/pidstore/pidstore.go	76.92%	2 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3132      +/-   ##
==========================================
+ Coverage   51.08%   51.47%   +0.38%     
==========================================
  Files         177      177              
  Lines       11157    11170      +13     
==========================================
+ Hits         5700     5750      +50     
+ Misses       4958     4926      -32     
+ Partials      499      494       -5     

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

[Wondertan]

I can't think of any other reason why It could get corrupted besides an ungrateful shutdown. In this case just doing that only for pidstore might not solve the issue. Lets ask conduit if this fixes the issue for them without resetting the node and only after merge it

[renaynay]

@Wondertan I agree that an ungraceful shutdown is most likely the cause for this. IMO fix is still ok to implement as pidstore is non-essential.

[distractedm1nd]

There are other datastore corruptions that happen, I wonder if we can wrap badger startup similarly or something (not resetting it, but just by giving a more readable error output when detected)