Fix Db-analyser incorrect handling of resource registries

If the same registry was given to the validation logic, when committing a forker
weird things would happen. This creates a new registry just for that step

Author: jasagredo

ouroboros-consensus-cardano/src/unstable-cardano-tools/Cardano/Tools/DBAnalyser/Analysis.hs

@@ -436,11 +436,11 @@ storeLedgerStateAt slotNo ledgerAppMode env = do
   FromLedgerState initLedgerDB internal = startFrom
 
   process :: () -> blk -> IO (NextStep, ())
-  process _ blk = do
+  process _ blk = withRegistry $ \reg -> do
     let ledgerCfg = ExtLedgerCfg cfg
     oldLedger <- IOLike.atomically $ LedgerDB.getVolatileTip initLedgerDB
     frk <-
-      LedgerDB.getForkerAtTarget initLedgerDB registry VolatileTip >>= \case
+      LedgerDB.getForkerAtTarget initLedgerDB reg VolatileTip >>= \case
         Left{} -> error "Unreachable, volatile tip MUST be in the LedgerDB"
         Right f -> pure f
     tbs <- LedgerDB.forkerReadTables frk (getBlockKeySets blk)