Refactor: make "unlocked" functions in CheckpointManager to take 'Lock&' in input

It is good practice that an "unlocked" function takes a reference to the required lock in input. That doesn't completely resolve concurrent access issues (e.g., that doesn't force the user to acquire the "right" lock), but it is a good reminder for callers.