Normalizing callbacks for escape-hatch usage

Nobody has claimed this yet.

The current callbacks are `before_save`, `after_save`, `after_commit` for SaveOperation, `before_delete`, `after_delete` for DeleteOperation, and `before_run`, `after_run` for Operation. With the exception of `after_commit`, these all do the exact same thing in their perspective positions.

One thing we could do is make `before_save` and `before_delete` just call `before_run`. Likewise for `after_save` and `after_delete`. Then these essentially are just syntactic sugar aliases used for clarity and convention. The benefit here would be if you wanted something special to happen before any sort of operation, you could create a module that just calls `before_run` and include that in every operation type and it would work.

The `after_commit` works the same, but the issue is that it's called in a different spot. We wouldn't want this added in to the `after_run` chain.

Start by locating the callback definitions for SaveOperation, DeleteOperation, and Operation, then trace where before_run, after_run, and after_commit are invoked. The refactor is done when before_save and before_delete share the before_run behavior, after_save and after_delete share after_run behavior, and after_commit remains separate at its existing point.

Written by the indexing model from the issue text.