Cleanup tool/internal service for resources of crashed applications

## Brief feature description

When an application crashes, it can happen that a service is only partially removed and becomes unusable.
An internal service and/or a command line application shall cleanup the remainders of such services.

The following use cases shall be considered:

* remove static service info, when only the dynamic service info exists
* remove dynamic service info, when only the static service info exists
* remove the data segment of a publisher if the owning process no longer exists
* remove the publisher/subscriber as participant from the dynamic service info when the owning process no longer exists.

No files, tests, or entry points are named. Begin by mapping the proposed internal service or command-line application against the four listed crash-recovery cases; done means the stale static, dynamic, publisher, and participant resources are identified and cleaned up when their owning process no longer exists.

Written by the indexing model from the issue text.