Create a live sanity checker

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

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

Description

bevy_impulse is completely event-driven which is good for efficiency, but introduces a non-zero risk that a subtle uncaught bug somewhere in the implementation (perhaps an extremely rare race condition) could cause execution of a workflow to get permanently stuck.

While we strive to not have any bugs at all in the implementation, the reality of the risk should not be ignored. We should implement a system that can periodically audit the ongoing workflows to verify that all activities are running as expected and that no workflows have come to an unexplained stop. If anything is found to be out of order, the affected workflow should be cancelled and the situation should be logged in UnhandledErrors in as much detail as possible.

Things to examine:

• Can all ongoing scoped sessions reach their terminal nodes?
• Are all buffers of finished session cleared out?
• Are all inputs of finished sessions cleared out?
• Are all finished impulses despawned?

This tool should be applied to every test in the library. We should also make it something that users can configure to run periodically to prevent problematic halts in deployments, although it should not be run very frequently.

Start by reviewing the bevy_impulse workflow implementation and the UnhandledErrors path, then inspect the library's existing tests. Define how periodic audits should check ongoing and finished sessions, how affected workflows are cancelled and logged, and how users configure the audit frequency; done means the tool is applied across the tests and can be configured for deployments.