handle require.resolve fallback when walking node_modules with no main field in package.json

[thescientist13]

Related Issue

resolves #557 (comment)

Summary of Changes

1. Add fallback handling when require.resolve can find what we need

TODOs

1. Understand why it cant be found
   • seems related to how NodeJS treats packages with "unusable" main field in its package.json (see edit to above linked comment)
   • this is kind of "disappointing" because while these packages may not have a "main" or exports, in the case of @babel/runtime, they still have their own dependencies, so we still need to get the location to walk that package.json
2. Add test cases
3. How to best fallback in the above identified situation? Maybe as part of leverage import.meta.resolve to support import maps generation and accurate node_modules resolution when building #684 or keep leverage NodeJS resolve logic for looking up location of paths for node modules #557 open and move into the next project?
   • found it! require.resolve.paths should be a good fallback if require.resolve itself fails.