Handling RENEW ack type in EXPLICIT ack mode in Share consumers

[sobychacko]

Not related to the change in this PR (which is great), but raises the question as natural evolution afterwards.
How to deal with RENEW if we chose EXPLICIT?
Is there a possibility that we have to extend the lock somehow from the container perspective?

Originally posted by @artembilan in #4376 (comment)