Add stop and failure lifecycle events to share consumer container

[sobychacko]

The share consumer container publishes ConsumerStartingEvent and ConsumerStartedEvent but no stop or failure events.

wrapUp() only calls consumer.close() — no event publishing.

ConsumerStoppedEvent and ConsumerFailedToStartEvent take generic Object parameters and can be reused directly. ConsumerStoppingEvent takes Consumer<?, ?> and Collection<TopicPartition>, which won't work — ShareConsumer does not extend Consumer and share consumers have no partition assignments. This needs either a new ShareConsumerStoppingEvent or a refactor of the existing event.

[zooo-code]

Hi @sobychacko !
I'd like to work on this issue if it's open for contribution.

From looking at the code, I understand:

• ConsumerStoppedEvent and ConsumerFailedToStartEvent take generic Object parameters, so they can be reused directly
• ConsumerStoppingEvent takes Consumer and Collection, which won't work since ShareConsumer doesn't extend Consumer and has no partition assignments

Would you prefer creating a new ShareConsumerStoppingEvent, or refactoring the existing ConsumerStoppingEvent to be more generic?

Thanks!

[sobychacko]

@zooo-code Please go ahead. I like the idea of a separate component for share consumers. Thanks!