[CURATOR-689] Guard create/setData/delete with lock path

[jira-importer]

Curator has several lock recipes(LeaderLatch, InterProcessMutex and etc.), but it has no simple intuitive method to guard modification under lock path. I am certain that CuratorFramework.transaction is capable of this, but I still want a simple way to archive this.

I implemented one before in rust, but it might be relative hard to it to cooperate well with existing `CreateBuilder`, 'SetDataBuilder` and `DeleteBuilder`.

It need time to explore, post it here for memories.

---

Originally reported by kezhuw, imported from: Guard create/setData/delete with lock path

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

[jira-importer]

tison:

There is a related discussion at CURATOR-542 and I ever implement something like a transactional store at https://github.com/apache/flink/pull/9878.

[jira-importer]

[Originally related to: CURATOR-604]