Don't clean up stale lock file from another daemon in daemon entrypoint

[glyh]

This logic has been introduced into daemon recently.

mina/src/lib/mina_lib/conf_dir.ml

Line 82 in 9e0cb54

[%log info] "Removing lockfile for terminated process"

[cjjdespres]

This logic has been introduced into daemon recently.

mina/src/lib/mina_lib/conf_dir.ml

Line 82 in 9e0cb54

[%log info] "Removing lockfile for terminated process"

It doesn't seem that recent, judging from the git history. That being said, the line being changed in this PR is also old, and I agree that it seems redundant, since the daemon will clean up the lock file itself.

[glyh]

@SanabriaRusso , could you approve since Christian thinks so? He worked on related context before :)

[SanabriaRusso]

For keeping track of the issue: I have tested an artifact produced from this PR and still shows the constant restarts issue. I.e., of the lockfile is not removed and the Pod (tested in Kubernetes with persistence, in this case) is killed/restarted, the next instance is unable to start.

[glyh]

Drafting for now. I think it's another bug we're running into