Make Actions Consistent and Remove Redundancies #19
Description
The actions model is one of the more recently evolved bits of Bloom, and has had a few big changes. I feel it's settled down now, and would benefit from cleaning up NAMING of methods, removing a few redundant actions, probably splitting a few actions up, and certainly pulling out some common sub-action behavior (like, creating a thing, linking a thing to it, and so on, which happens in many actions.).
Actions started off as workflow_step related only, then also workflows, then all. As such, some actions might properly belong moved to a different object level, as I kind of messily instantiate bloom objects as bloom_obj_wfs still in many places.
A larger refactor should wait for a while longer to see how things shake out with how the actions stand now.
relatedly: These actions are natural API endpoint behaviors beyond object CRUD, how to expose them?