Support automatic cleanup of SIP-created Kafka consumer groups during pod shutdown

Business Requirement
Customers operating SIP in containerized environments experience the accumulation of inactive Kafka consumer groups following pod restarts, scaling events, and pod termination. Over time, these inactive consumer groups increase operational overhead and monitoring complexity.

Current Limitation
IBM has confirmed that the creation of dynamic consumer groups is working as designed and is required for caching-related functionality. However, SIP does not currently provide a mechanism to automatically remove or clean up inactive consumer groups when pods are terminated.

Requested Capability
Provide a supported mechanism to:

• Automatically clean up SIP-created consumer groups during graceful pod shutdown.
• Optionally configure retention or cleanup behavior for inactive SIP consumer groups.
• Reduce the number of orphaned consumer groups retained in Kafka after pod lifecycle events.

Background / Support Case Reference
Customer requested automatic cleanup of SIP-created Kafka consumer groups during pod shutdown to avoid accumulation of inactive consumer groups in Kafka. The request was previously discussed with IBM Support under TS020160792. The current behavior was confirmed as "working as designed"; however, no product capability exists to automatically clean up inactive SIP-created consumer groups. As a result, customers must rely on Kafka administrative cleanup processes.