Code Quality: Downgrade LiteDB to fix transaction issue

[hez2010]

Resolved / Related Issues
We hit litedb-org/LiteDB#2435 which results in Files crashing. As a workaround, we may use Shared connection instead of Direct. It may slow down the query speed, but it no longer crashes.
Closes #15203
Closes #15172
Closes #15157

Validation
How did you test these changes?

• Did you build the app and test your changes?

Screenshots (optional)
Add screenshots here.

[yaira2]

It may slow down the query speed, but it no longer crashes.

Do you have any idea how much of a difference it makes?

[hez2010]

Do you have any idea how much of a difference it makes?

In my simple test 100 times of insertion and query (200 ops in total) regressed from 0.01 seconds to 0.2 seconds (20x slower).

[hez2010]

Maybe we can instead downgrade to LiteDB v5.0.17 so that we don't have to suffer from the performance regression?
Or we can maintain a fork of LiteDB by ourselves until the bug get fixed in upstream.
Or maybe we can change our database provider to something else such as FASTER.

[hez2010]

While I'm hitting another issue in LiteDB after switching to Shared connection:

System.Threading.SynchronizationLockException: 'The lock is being disposed while still being used. It either is being held by a thread and/or has active waiters waiting to acquire the lock.'

Seems that switching to Shared connection is not a correct fix.
We should consider either forking or downgrading LiteDB or changing database provider.

[yaira2]

Sounds like downgrading is the best option for now

[hez2010]

There's still a rare possibility getting crash due to System.ExecutionEngineException caused by LiteDB if you quickly switch between folders hundreds or thousands of times, but generally it should work now. (not sure why it happens as such exception doesn't have a stacktrace).