Bug: Incorrect condition for unlocking user update api lock

[kartik-579]

📜 Description

If an error is faced while updating user, the user might get stuck in lock state.

👟 Reproduction steps

1. Update an user with surity of it facing an issue and encountering error.

👍 Expected behavior

The user should be available to be updated again.

👎 Actual Behavior

The user gets stuck in locked state.

☸ Kubernetes version

1.24

Cloud provider

🌍 Browser

Chrome

🧱 Your Environment

No response

✅ Proposed Solution

No response

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

AB#5011

[kartik-579]

RCA: In #3760, the unlock condition was being called at the end of function but in case of some error in the actual flow, unlock won't be happening causing the user to get stuck in locked state and never get updated.