Long Running Operations: Ensure eager write lock

[lauraneto]

Summary

• Use EagerWriteLock instead of WriteLock for long running operations lock acquisition

Details

This change ensures proper lock acquisition timing when checking if a long running operation of the same type is already running. With the introduction of lazy locks in #21102, this lock needs to be explicitly eager to maintain the expected behavior.

[nikolajlauridsen]

Looks good 👍

[Copilot]

Pull request overview

This PR fixes a potential race condition in the long-running operation service by changing from lazy lock acquisition (WriteLock) to eager lock acquisition (EagerWriteLock). Following the introduction of lazy locks in #21102, locks requested via WriteLock are queued and only acquired later when needed (e.g., when database access occurs). However, the long-running operation service needs to immediately hold the lock before checking if an operation of the same type is already running to prevent concurrent operations from bypassing this check.

Key Changes

• Changed scope.WriteLock() to scope.EagerWriteLock() in LongRunningOperationService to ensure immediate lock acquisition before the IsAlreadyRunning check