fix: resolve lmdb binaries correctly

[ascorbic]

The fix for #294 did not cover all cases. Specifically, the lmdb module was resolving the incorrect path, so when using a version of Gatsby that uses it, we were trying to look in the wrong place for the binaries. We need to know their location because we copy them into the function bundle. This fix handles the case where lmdb resolves its root to the subdirectory, by looking a level up.

[netlify]

✅ Deploy Preview for netlify-plugin-gatsby-demo ready!

Name	Link
🔨 Latest commit	4bd93d3
🔍 Latest deploy log	https://app.netlify.com/sites/netlify-plugin-gatsby-demo/deploys/623842211e9e280009852188
😎 Deploy Preview	https://deploy-preview-327--netlify-plugin-gatsby-demo.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[orinokai]

All looks good. Just worth mentioning that we could maybe dry up the code and make it more generic by replacing findModuleFromBase with something like the resolve-package-path module, but we might not want to introduce an external dependency when what we have already works in this case?

[ascorbic]

All looks good. Just worth mentioning that we could maybe dry up the code and make it more generic by replacing findModuleFromBase with something like the resolve-package-path module, but we might not want to introduce an external dependency when what we have already works in this case?

True, that could be more robust against changes in future. We should do some tests at some point to see if it covers all of our cases.