Fix glob resolver package issue with deep entry points

[marcins]

↪️ Pull Request

This is a follow-up from #8097 - when trying to implement the change in my repository I realised there was a step missed, if the package entry point resolves to a file not in the root, then the paths for the glob import will need to be relative to the entry point, where they should be able to be relative to the package root.

This change adds an additional step to perform a findPackage on the resulting filePath in order to resolve to the root of the package.

💻 Examples

Before if you had a package @scope/pkg with an entry point of ./dist/index.js then the glob resolver would resolve the root to @scope/pkg/dist/, so if you used a path like @scope/pkg/src/foo*.js it would actually resolve to @scope/pkg/dist/src/foo*.js which is incorrect. With this change the path resolves as expected.

🚨 Test instructions

Failing integration test with a deep entry point was added, change was made and confirmed all integration tests still pass.

✔️ PR Todo

• Added/updated unit integration tests for this change
• Filled out test instructions (In case there aren't any unit tests)
• Included links to related issues/PRs

[marcins]

I wasn't sure what to do about this - findPackage requires a context, so I provided one with the invalidation info from the step above, however when we return the resolution at the end of this method around line 178, there's only invalidateOnFileCreate: [{glob: normalized}], included. Should we collect all these additional invalidations and add them there as well?

[devongovett]

I'm not sure this is quite right because there could be another package.json inside a sub-directory of the module. We can use the resolver.resolveModule method for this I think.