First unresolved import gets the typing file into cache and sets it as root,
This results in scheduling new typing request with that unresolved import missing
The result will come back with typing file that is omitted, so root file will change but file will still be part of program so its not really removed from program

Also cache the inferred type acquition for inferred project

…ypings cache

This change finally makes all tests pass incremental tests for matching resolutions and program structuture

… of another pass

…eed to update last cached unresolved imports just because we have new program

…p logging added

…s in the program

This shows cache is holding onto resolutions that are no longer needed by program because either those modules arent present in file or is determined to be ambient resolution

…ns are reused/are resolved to ambient module names

…ay instead of defering external module reoslutions to watch all failed lookup locations

- All the package json watched are ref counted if watched
- Not watched package json locations are released
   - First of this kind are when resolution from global cache fails, we dont watch those locations so not safe to have them cached
   - If we are looking for a file and the file is not found, the package json locations looked up are not watched

…root directory for watching resolutions

…sharing caches

// TODO: update incremental tests to actually verify the cache