Introduce the Env::nested_read_txn from an RwTxn

[Kerollmops]

This PR is a first attempt at patching LMDB to generate multiple RoTxn from an RwTxn and, therefore, be able to read the content of an uncommitted RwTxn in parallel. You can find the LMDB patch in the dedicated fork. We can run many algorithms in Meilisearch to process the written content and generate new data structures before committing the transaction.

Warning

We found a memory leak in the underlying LMDB PR. We need to take time to investigate the matter and fix it.

This PR is open, but we also have it on crates.io under the v0.22.1-nested-rtxns version. This version is experimental and will not be maintained in this state until we merge the changes into upstream LMDB. For the time being, we will continue to maintain it in this manner.

// opening a write transaction
let mut wtxn = env.write_txn()?;

// [use the RwTxn to write into the env]

// opening multiple read-only transactions without committing beforehand
let rtxns = (0..1000).map(|_| env.nested_read_txn(&wtxn)).collect::<heed::Result<Vec<_>>>()?;

// [use the RoTxns and move them onto different threads]

This first attempt uses a broken fork of LMDB that ignores the number of nested write transactions associated with the parent one. Therefore, it lets heed create multiple nested write transactions from the parent one (dangerous). We store those write transactions in RoTxns shells to disallow writing anything with them at the compilation level.

However, while thinking about this, it is probably still possible to open databases (already existing) and commit them from multiple threads concurrently. It should be either disallowed or will, anyway, be fixed by the correct LMDB patch later.

To fix the Windows CI we will have to use the experimental stdatomic headers. Actually, no. We had to enable the /std:c11 and /experimental:c11atomics features.

Note that the CI is broken, but it works locally, so it's maybe a submodule issue (it's always a submodule issue) 🤔 It was...

To do

• Speed up the new nested-rtxns example in the CI (build it in release)