[CURATOR-465] Curator needs an abstraction that interrupts locking threads when there are connection problems

For some reason, we don't have an abstraction that manages interrupting a thread that's using one of Curator's lock recipes. Our docs say that if you get SUSPENDED/LOST you should interrupt any locks/leaders. LeaderSelectorListenerAdapter handles this but we don't have something for locks or LeaderLatch. 

I think something like the Locker class would work where when the lock is acquired, the current thread is recorded. The class adds a ConnectionStateListener and interrupts the thread when the connection is lost.

---
Originally reported by randgalt, imported from: Curator needs an abstraction that interrupts locking threads when there are connection problems

• status: Open
  
• priority: Major
  
• resolution: Unresolved
  
• imported: 2025-01-21