Better organization of operations that should trigger on certain actions

[TrevorBurgoyne]

There are many updates/filterings/drawing etc that needs to occur every time specific actions occur, ie editing, moving, deleting, etc. Currently if you want to add/remove such behavior, you have to track down a billion places where a function call should occur.

Since actions are already recorded via record_action(), we can probably gather some of these redundant groupings of function calls into record_action() and just have a big switch statement with all possible action types and their associated "listeners". This would make debugging/development of such behaviors a heck of a lot nicer i think