fix(pnp): check if path belongs to a pnpapi instance before checking the filesystem

[merceyz]

What's the problem this PR addresses?

• Using the portal: protocol to an external project could end up using that projects pnpapi, which if the project has peer dependencies, would cause MODULE_NOT_FOUND errors if the pnpapi context was lost and had to be located.
• Using the global cache (enableGlobalCache: true) is fragile and does not handle loosing the pnpapi context while in the global cache

Fixes #706
Fixes #965
Fixes standard-things/esm#871 (cc @jonaskuske)

How did you fix it?

Ask each pnpapi instance if they control the modulePath, if more than one pnpapi controls the path throw an error, if only one controls it use that instance, otherwise fallback to searching the filesystem.

Checklist

• I have read the Contributing Guide.
• I have set the packages that need to be released for my changes to be effective.
• I will check that all automated PR checks pass before the PR gets reviewed.