Stale server-list.LOCK prevents application from functioning

Nobody has claimed this yet.

### Search first

- [x] I searched and no similar issues were found

### What Happened?

After starting Logseq 2.0.1 (in Windows 11) no graph database would load / display. The application would crash when clicking on flashcards with an error. See below.

I tried a lot of resolutions to resolve this. New .logseq and logseq below user profile etc. In the end I found a file named server-list.LOCK and removed it since I am not syncing or whatever.

This resolved the issue.

```
Error caught by UI! No protocol method IIndexAccess.-datoms defined for type null: Error: No protocol method IIndexAccess.-datoms defined for type null: at APP.a (lsp://logseq.com/js/main.js:7665:430) at xh (lsp://logseq.com/js/main.js:7952:284) at ji (lsp://logseq.com/js/main.js:15379:330) at Li (lsp://logseq.com/js/main.js:8019:373) at gm (lsp://logseq.com/js/main.js:8264:372) at lsp://logseq.com/js/main.js:21675:122 at lsp://logseq.com/js/main.js:8984:452 at gu (lsp://logseq.com/js/react-dom-client.production.min.js:2:96828) at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113141) at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025) at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113186) at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025) at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113186) at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025) at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113186) at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025) at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113186) at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025) at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113121) at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025) at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113121) at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025) at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113121) at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025) at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113121) at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025) at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113121) at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025) at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113121) at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025) at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113121) at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025) at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113121) at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025) at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113121) at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025) at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113121) at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025) at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113186) at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025) at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113121) at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025) at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113121) at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025) at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113121) at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025) at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113121) at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025) at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113121) at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025)```

### Reproduce the Bug

no idea, place a server-list.LOCK file in logseq folder below user profile?

### Expected Behavior

_No response_

### Screenshots

_No response_

### Desktop or Mobile Platform Information

_No response_

### Additional Context

_No response_

### Are you willing to submit a PR? If you know how to fix the bug.

- [ ] I'm willing to submit a PR (Thank you!)

Begin by reproducing the Windows 11 failure with a server-list.LOCK file in the Logseq folder below the user profile, then compare behavior after removing it. Trace the code responsible for that lock file and the graph database load path; done means the graph loads and flashcards no longer produce the reported IIndexAccess.-datoms error.

Written by the indexing model from the issue text.