fix: Remove kura.lock

[dima74]

Description

Originally kura.lock was introduced to prevent multiple iroha instances running with the same data directory. However if iroha doesn't remove kura.lock, e.g. in case of non-graceful shutdown, it causes problem that iroha couldn't start after restart. Also usually iroha is deployed using k8s cluster where each peer lives in different container so original problem is not relevant in this case. So it is proposed to remove kura.lock.

Linked issue

Related: #4830
Related: #4848

Benefits

Remove kura.lock, allowing Iroha to restart after non-graceful shutdown

Checklist

• I've read CONTRIBUTING.md
• I've used the standard signed-off commit format (or will squash just before merging)
• All applicable CI checks pass (or I promised to make them pass later)
• (optional) I've written unit tests for the code changes
• I replied to all comments after code review, marking all implemented changes with thumbs up

[Erigara]

lgtm