add undo_info parameter to tabular changelog

[kaikue]

By setting undo_info=1 in calls to tabular_change_log or tabular_change_log_many, two new columns will be added to the result: is_undo and undone_by. is_undo contains undo, redo, or the empty string, depending on what type of operation it is. undone_by contains either the ID of the operation that undid it (if it has been undone), or the empty string (if not).

This parameter is set to false by default, since it is a somewhat expensive operation (in order to associate edits with their undos, it needs to loop through every edit in the dataset).

[sdorkenw]

This looks like it works but logic like that ideally lives in the associated module (segmenthistory in this case). I think there is a way to integrate this directly into the loop through the operation entries in there:
https://github.com/seung-lab/PyChunkedGraph/blob/pcgv2/pychunkedgraph/graph/segmenthistory.py#L158
as by definition the edit and its undo are in the same lineage.