[7.17] chore(NA): updates from lmdb-store to lmdb (#145891)

[watson]

Backport

This will backport the following commits from main to 7.17:

• chore(NA): updates from lmdb-store to lmdb (#145891)

Questions ?

Please refer to the Backport tool documentation

\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>"}},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com//pull/145891","number":145891,"mergeCommit":{"message":"chore(NA): updates from lmdb-store to lmdb (#145891)\n\nThis PR upgrades from `lbmd-store` into `lmdb` which is the new package\r\nand fully compatible with node `v18`.\r\nSo far my tests shows the new implementation is compatible with our\r\nusages and I'm actually seeing a great performance boost when comparing\r\nwith main specially on subsequent calls of the same command.\r\n\r\nThis can be tested by running the following 2 times on main vs this\r\nbranch `time node scripts/kibana --config\r\nsrc/cli/serve/integration_tests/__fixtures__/invalid_config.yml\r\n--migrations.skip=true --verbose`\r\n\r\nI verify the following on my machine\r\n\r\n**main:**\r\n_1st run:_ 36s\r\n_2nd run:_ 34s\r\n\r\n**this branch:**\r\n_1st run:_ 35s\r\n_2nd run:_ 6s\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"e65c6526107670689c520bc20c973626c12c636d"}},{"branch":"7.17","label":"v7.17.9","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->

[watson]

@mistic I went ahead and tried to backport #145891 to 7.17 in this PR so we can upgrade its Node.js to version 18. I've looked at the single Jest test failure for hours now and I can't figure out why it's behaving like it does. It's not the jest test itself but rather something with the module system, potentially in combination with jest overriding some things inside the module module (maybe we need to upgrade jest as well??). Would you be able to take a look soon to see if you can figure out what's wrong?

[mistic]

@watson I found this comment I left back then #146647 (comment)

I think to backport this into 7.17 we will need to upgrade first jest@27 in this branch

[watson]

@mistic how much work do you think upgrading to jest 27 would be? Unfortunately we do need to upgrade the Node.js version on 7.17 as the current version (v16) will no longer receive any bug or security fixes after 2023-09-11

[mistic]

@jbudz as you were the one working on this, do you anticipate too much work to upgrade jest to v27 on 7.17?

[kibana-ci]

💔 Build Failed

• Buildkite Build
• Commit: 167d37b
• Interpreting CI Failures
• Storybooks Preview

Failed CI Steps

• Jest Tests #6

Metrics [docs]

✅ unchanged

History

• 💔 Build #101018 failed ea2031a
• 💔 Build #100962 failed 7475600
• 💔 Build #100951 failed e7de50f

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @watson

[mistic]

Closing in exchange of #146647