Handle file resource contention on arcade pod restarts

[patstevens4]

Arcade will occasionally enter an error state across pod restarts where a thread from the previous arcade instance doesn't release file lock by the time the new arcade instance tries to lock the database files.

Workaround:
Restart the pod/service again

AC:

1. Arcade self heals if a file resource lock contention error occurs