[Experiment] Some tweaking to handle project references for auto import

[sheetalkamat]

• Add directly referenced project's root files to the auto import provider if "paths" are setup in options which kind of indicates willingness to use module resolution
• Allow auto import if paths is present in options or symlink cache has any symlinks discovered (as part of say calculating auto import root names)

Fixes #55879

[sheetalkamat]

May be we also need some tweaking if referenced project was discovered while node_modules were detected and we ignored everything but entry point.

[sheetalkamat]

We also could get info from opened referenced project instead of adding to auto import provider but I wanted to first check if we want something like this which understands referenced project or not before adding anything more to this experiment

[andrewbranch]

We also could get info from opened referenced project instead of adding to auto import provider

This was the approach I took in #47690 which ended up being problematic for the export info and module specifier caches. I forgot about this distinction when we talked the other day. I think using the AutoImportProvider is slightly less efficient but avoids these caching pitfalls, and is overall a more promising approach. I spent a little while trying to break the export info cache invalidation on this branch and it looked good. That said, exportMapCache.ts and moduleSpecifierCache.ts could be updated to exercise this new functionality.

[sheetalkamat]

@andrewbranch ready for review

[sheetalkamat]

@andrewbranch i had missed the editor services to update to check for same flag when i first pushed commit .. didn’t realize you already looked at it or I would I have made separate commit .. i will also add a test when that option is not set in host preferences just for completeness when I get to desk