Vulkan: Remove release commands from checkOneCommandBatchLocked This is a follow up for: Add a new mutex in CommandQueue to protect Vulkan Command Pool crrev.com/c/angle/angle/+/6020895 `SyncHelper::getStatus()` may call `CommandQueue::checkOneCommandBatchLocked()` which in turn may call `releaseFinishedCommandsLocked()` if `mFinishedCommandBatches` is already full. This requires locking the `CommandPoolAccess::mCmdPoolMutex` mutex. This may delay API execution even when "timeout == 0", which is against EGL spec. Bug: b/362604439 Change-Id: Icf8f3657b65f2e435930adb12266a100dc861a93 Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/6048803 Reviewed-by: Shahbaz Youssefi <syoussefi@chromium.org> Reviewed-by: Charlie Lao <cclao@google.com> Commit-Queue: Igor Nazarov <i.nazarov@samsung.com> Reviewed-by: Yuxin Hu <yuxinhu@google.com>