Hi, I think it's needed to wrap semaphore usage into finally block in order to avoid deadlock

[victor-makovsky-covergo]

Product

Hot Chocolate

Version

12.0.0

Link to minimal reproduction

https://github.com/ChilliCream/graphql-platform/blob/c477e13e161fe6ff682a6849facad19c63d9f83d/src/HotChocolate/Core/src/Execution/Configuration/DefaultRequestExecutorOptionsMonitor.cs#L82C13-L82C34

Steps to reproduce

May be this is very edge case but sometimes it reproduces on my project and leads to deadlock (graphql requests start but never finish and hanging waiting for sempaphore).

What is expected?

Semaphore is always released, release statement is put into finalize statement.

What is actually happening?

Deadlock

Relevant log output

Additional context

No response

[victor-makovsky-covergo]

It is possible to reproduce exception and deadlock when application just started and then first graphql request is sent and then cancelled (browser cancelled request), this leads to semaphore in the options monitor being always at 0 counter which prevents all graphql requests from processing and requires application restart to fix.