Comment 2 for bug 1902233

Since Evergreen doesn't have a native undelete concept this will be awkward. We could add a trigger that triggers off an undelete but it won't have any idea if the undelete is because of a merger reversal or not. Note that if we add something like a utility function to unmerge record merges that bundles undeleting a record and unsettling the merge to I think we should take that as an opportunity to add some merge tracking, specifically tracking volumes moved and title level holds and move those back as appropriate.