Support non-shared callbacks

Currently callbacks are implemented in a way that they can be shared, i.e. reused by multiple different requests and/or workflows. This made a lot of sense in the first iteration of bevy_impulse when everything was one-shot and repeatedly creating and dropping systems doesn't make much sense.

Now that workflows are fully reusable, there may be legitimate use cases where someone wants to drop a callback system into a specific node of a workflow and not reuse the system anywhere else. In those cases, there is an unnecessary mutex locking being done each time the node is run.

We can avoid the mutex lock if we have two flavors of callbacks: unique and shared.

Start by locating the callback implementation and the workflow node execution path. Trace how callbacks are reused and where the mutex is acquired, then determine the API and behavior needed for unique and shared callback flavors. Done means unique callbacks avoid unnecessary mutex locking while shared callbacks remain reusable across requests or workflows.