[Feature request]: Introspection and debugging API

Before proceeding, is there an existing issue or discussion for this?

• I have done a search for similar issues and discussions.

Description

It would be good if there is a introspection and debugging API to allow

• Querying the list of currently running nodes
• Query the amount of times a node is activated and the time it took for it to produce an output
• Setting a breakpoint to pause execution when a node is activated
• Query the source or reason the node is activated
• Resuming a paused node
• Forcing a node to produce a given output
• Forcing a node to receive a given input
• Change the buffers and streams used by a node

Implementation Considerations

The API should be accessible from outside the workflow, i.e. from a non bevy managed thread. If the API requires any hooks that might impact performance, it should be made optional.

Alternatives

Detailed logging and tracing for when a node is activated, how long it took, reason for activation etc.

Additional information

No response

The issue names no files, tests, or entry points to begin with. First clarify which checked capabilities are in scope and how the API should operate outside a Bevy-managed thread, including optional performance-impacting hooks. Done requires an agreed API scope and design for introspection, breakpoints, and resuming before implementation can be estimated.