When creating program, we have two methods to get resolved project reference. Through CompilerHost.getParsedCommandLine or getting host.getSourceFile and using tsconfig parsing on that source file. Previously only tsc -b used getParsedCommandLine that cached the command lines for the projects. With this change tsserver as well as tsc -w set those methods on CompilerHost.
The change involves:

1. Program now handles releasing of ParsedCommandLines if they are not needed in new program just like we release source files. This is to enable handling and releasing of the parsed command lines between multiple programs that is used by tsserver and tsc -w
2. When checking program upto date ness, checking only source file is not enough, we also need to check files names in the command line for resolved project references since they can change without changing source file when host caches the ParsedCommandLine (on addition or deletion of file in wild card directory we just update file names instead of having to parse complete config file again)
3. Our current utility method isIgnoredFileFromWildCardWatching can take root file names so it can ignore the output file names for those and ignore them.
4. In tsc -w and tsserver scenario, we cache the ParsedCommandLine for the referenced projects and its invalidated only if there is change in config file, change in extended files or new files are added or removed
5. Because extended config files are watched, we now use extended config cache map when parsing config files and invalidate this cache if extended config files change (or file that is exteneded directly/indirectly) changes
6. Language service uses getParsedCommandLine on LanguageServiceHost if present or get source file and parses the command line (just like it would have been done by program before this change)
7. In tsserver, project service the cache of config file existence is updated to contain parsed command line and watching of config file is unified in the existence cache (Before this change watcher would present in cache only if there is no configured project is around for that config file). So if there are parsed command lines needed by any project or if there is a open script info which is root of inferred project that depends on changes to config file, it is watched.
8. The wild card directory and extended config file watching also is cached in config file existence cache so it can be unified for all projects that use parsed command line for that confg file

Fixes #37304
Probably fixes #42607