[Feature] Add method for dependency to self terminate and notify caller

[francois-normandin]

When a dependency is owned by a caller object, there is currently no way for the dependency to self-terminate and notify its caller. The caller is the only one able to terminate with use of "shared key". There should be a way for the dependencies to terminate independently through the use of its "private key". This action should notify the caller which should automatically remove the dependency from its list. This addresses the use case of a caller dispatching work to another SMO and expecting it to self-terminate on completion of the task. Current workaround is to implement an event that the callee can generate for its caller to monitor, thus creating a tight coupling.

[francois-normandin]

This method is created (release 1.1.7) but feature is incomplete: requires a mechanism to notify parent process when owned. Parent process should remove dependency if dynamically-added.

[francois-normandin]

This will be released in version 1.1.13 Adding hooks for:

• onDependencyStarted( )
• onDependencyStopped( ) Adding auto-cleanup of dependencies list on Dependency Destroyed event. (no hooks provided, since dependency reference does not exist anymore.