Improve usage of history states throughout the application

[Keavon]

History states (undo/redo) are implemented, but many tools and actions and messages don't save history states when they need to. The resulting experience is quite unpleasant since it's easy to lose work or end up undoing/redoing way more than expected. This task involves experimenting with lots of everything, basically doing a QA test on everything, and fixing all the problems with history wherever one shows up. Related: #559

[RahulHi]

I'll work on this one.

[Keavon]

How is this going @RahulHi? Need any help?

[Keavon]

Hi @RahulHi, just another friendly check-in. Let me know if there's anything I can do to help push this along. Cheers!

[RahulHi]

@Keavon Will do! There isn't anything right now, but I will be sure to let you know of any questions I have!

[noblehelm]

Should every action produce a history to enable undo/redo? Even actions like using the Navigate Tool?

[Keavon]

@noblehelm Technically, using the Navigate Tool modifies the document, but we ideally would like to filter out some obvious things like that from counting for history. But it's probably better if we can make that opt-out rather than opt-in since currently it's too easy to implement features and forget about making them support history. The history system is quite crippled right now and really any improvements would be of vital importance.

[Keavon]

Closed by #932