Ability to integrate with more sources to trigger actions

[endernoke]

In order to integrate with more external events, e.g. when a user starts/finishes a vibe coding session in cursor, VibeRot needs to accept different sources of events for triggering and stopping actions beyond commands.

Currently, only system processes are supported, and shell commands are converted into fake processes with a hack.
The rules config also only supports a string-based commands/processes matching.

The project architecture should be refactored so that the action orchestrator accepts different sources in a unified and extensible manner. Optimally it would also expose an interface for the dynamic addition and removal of more sources.

[endernoke]

From quick research I don't think VS Code integration is feasible since the VS Code API doesn't provide a mechanism for extensions to be notified when copilot agent starts or finishes, or when a chat message is sent