Acquiring a write lock in the Journal blocks installing a received snapshot for ever

[romansmirnov]

Describe the bug

Based on the observations made in #7992, the follower could not install a received snapshot: #7992 (comment)

According to the thread dump in #7992, the installation of the snapshot is blocked when trying to acquire a write lock:

The write lock cannot be acquired, because a read lock is already held which was acquired when trying to open a reader. But the read lock will never be released because opening the reader failed with the exception "java.lang.IllegalStateException: Segment not open:

https://github.com/camunda-cloud/zeebe/blob/2dee25fcb748d8a9c6457eee465d08fd5a4d5471/journal/src/main/java/io/camunda/zeebe/journal/file/SegmentedJournal.java#L211-L218

To Reproduce

1. Acquire a read lock, when trying to open a reader
2. Let opening the reader fail
3. Try to install a new snapshot, which will acquire a write lock on the same journal

Observed Behavior:

• The Raft thread cannot acquire the write lock, because a read lock is held already.
• This blocks the Raft thread so that the snapshot cannot be installed.
• Additionally, an Actor Thread that executes an Actor Job to compact the log is waiting for the completion of a future which must be completed by the blocked Raft thread.
  

Expected behavior

• When opening the reader fails unexpectedly, the read lock is always released.
• The Raft thread and other threads are not blocked by it.

Environment:

• Zeebe Version: 1.2.5

---

related to #7992