Prune write-ahead log entries after application
The TransactionManager
currently doesn't prune the write-ahead log entries after they've been applied to the repository. This leads to the write-ahead log entry growing indefinitely as new transactions come in. In the current state without Raft, the write-ahead log entries can be pruned as soon as they've been applied to the repository. We should implement this prior to deploying the WAL.