Incorrect call to action button for Auto-Unlocked Tasks Mapped by the Same User

[manjitapandey]

Describe the bug
When a user attempts to map a task that was previously auto-unlocked, the call-to-action button incorrectly displays "Resume Mapping" instead of "Map Selected Task". Clicking "Resume Mapping" causes a page crash due to a conflict in the task's status.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'tasks page'
2. Click on 'a task to map'
3. Leave it for 2 hours until it gets auto unlocked
4. Click on same task where the status is available for mapping
5. See error - the button should say map selected task instead of resume mapping
6. Clicking on resume mapping crashes the page

Expected behavior
The call-to-action button should display "Map Selected Task" when the task becomes available again, preventing the status conflict and crash.

Screenshots

Additional context
Mapping the task task by different users solve the issue.

[ramyaragupathy]

@prabinoid - can you please confirm if we auto unlock tasks through a cron job? I believe this could be the reason, may be the DB is not up to date.

cc @royallsilwallz @manjitapandey

[manjitapandey]

Current Behavior:
For tasks locked for mapping, once the lock expires, the task is automatically unlocked. When clicking on the same task again, the action button correctly updates to Map selected task.
However, in the case of validation, even after the task is automatically unlocked, the action button still shows Resume validation. Clicking on the task then opens the iD editor with a pop-up message stating that the session has expired, offering options to either close or continue.
What should the expected behavior be in this case?

cc: @ramyaragupathy , @royallsilwallz