Node10Result on resolvedModule issues

[sheetalkamat]

Bug Report

🔎 Search Terms

🕗 Version & Regression Information

• Add additional diagnostic for packages that only resolve under non-exports-respecting modes #52173 added extra resolution and informtion from it to resolved module and that can interfere with how incremental works

⏯ Playground Link

Playground link with relevant code

💻 Code

// We can quickly address your report if:
//  - The code sample is short. Nearly all TypeScript bugs can be demonstrated in 20-30 lines of code!
//  - It doesn't use external libraries. These are often issues with the type definitions rather than TypeScript bugs.
//  - The incorrectness of the behavior is readily apparent from reading the sample.
// Reports are slower to investigate if:
//  - We have to pare too much extraneous code.
//  - We have to clone a large repo and validate that the problem isn't elsewhere.
//  - The sample is confusing or doesn't clearly demonstrate what's wrong.

🙁 Actual behavior

• node10Result is present as additional property on resolvedModuleWithFailedlookupLocations but that is not taken into account by builder so changes to only that build will not update incremental errors (eg install @types or some such
• The error stored in build info contains the file path for the file that is not changed relative to buildInfo can can make it not portable.

🙂 Expected behavior