Blackboard resource cleanup when static config was deleted

To create a blackboard service, as with any service, the static and dynamic config are first created. If this succeeded, the blackboard payload and management data segment are created. If this fails, the system is corrupted. For non-safety-critical usage, we could just clean up the blackboard specific resources instead of failing. This behavior could be chosen by a configuration parameter.

No source files, tests, or entry points are named in the issue. Start by locating blackboard service creation and the static/dynamic configuration lifecycle, then trace creation of the blackboard payload and management data segment. Done should be defined with maintainers: a configuration choice for non-safety-critical use and tests showing cleanup after a later creation failure without corruption.

Written by the indexing model from the issue text.