fix(nextjs): Fix resolution of request async storage module

[lforst]

Fixes #9120
Adresses #9092 (comment)

Previously we failed to properly locate Next.js' request-async-storage module in monorepo setups because we were limiting our search to a subset of paths in webpackConfig.resolve.modules.

Example:

• webpackConfig.resolve.modules contained ["<absolute_path_to_monorepo>/packages/<project_with_next_js>/node_modules", "<absolute_path_to_monorepo>/packages/<project_with_next_js>"]
• request-async-storage is located at /<absolute_path_to_monorepo>/node_modules/next/dist/client/components/request-async-storage.external.js
• Since since request-async-storage was not in webpackConfig.resolve.modules or any subpaths, we marked it as not resolved.

New solution: We look upwards from the webpack resolvable paths in the folder tree using the default node resolving algorithm to look for the nearest next installation. Once found, we try to look for the the request-async-storage modules inside that installation.

Additional considerations

I don't know whether it is enough to check the webpack resolvable locations. Even worse, I don't know whether looking upwards from the webpack resolvable locations is problematic because it might not resemble what webpack is doing.

Adding a dependency

We are using the resolve package because it let's us look upwards from a certain location without using stuff like require.resolve which might trip up webpack.

[Lms24]

Let's give it a try!