Undo/redo, bulk edit and onWill-file events

[jrieken]

This PR makes it possible that additional workspace edits from an onWill[Create|Rename|Delete]Files are added to the same undo/redo groups as the initiating operation. The sample is the Java file rename which makes a text edit before the actual rename. Those should only require a single undo.

This is PR is kinda large but simple. It spreads data because

• all onWill-events are triggered from the working copy service
• that service doesn't know anything about undo/redo (on purpose)
• the bulk edit service does know about undo/redo and consumes the working copy service
• some undo/redo information needs to travel to onWill-event listener
• therefore the bulk edit service can now pass data about undo/redo which the working copy service simply forwards to its event handlers

fyi - the alternative would have been to move all onWill-event logic into the bulk edit service but since there are still direct consumer of the working copy service it would have meant that the API now fires less event, like for "save as".

Somewhat open questions

• on the ext host the onWill-events will not fire anymore when undoing/redoing. That's to safe the undo-stack but might be unexpected?
• should the same happen for onDid-events that are caused by undoing/redoing? Those cannot piggy-bag extra edits tho.

[jrieken]

@bpasero please check the changes in the working copy service

[jrieken]

fyi @isidorn

[bpasero]

@jrieken seems ok to me, but would it make sense to put undoRedoGroupId: number | undefined, isUndoing: boolean | undefined into a single object to keep it together? It seems that it could be encapsulated in some object that describes the undo/redo state?

[isidorn]

@jrieken Thanks for looking into this. Once this lands I can double check the Java rename flow.

[jrieken]

related/tackles #107740

[jrieken]

but would it make sense to put undoRedoGroupId: number | undefined, isUndoing: boolean | undefined into a single object to keep it together?

I was also wondering about that but I didn't wanna make the undo/redo world more prominent in the working copy service. When more flags come I will do.