Handle config file change and default project management

[sheetalkamat]

This is everything from #57196 except there is no change in functionality for finding default project. So that we can get this for 5.5 but behavior change for 5.6

This change includes:

• Unless we have detected change in config file or we are reloading, once file is opened, its default config file name is never recalculated
• All the paths to find default project - opening a file, reloading a project, just searching what's default project for a file or change in config file, use singular path for finding default project
• When config file change is detected, we recalculate what is the default config name for open file and schedule update for project only if its new. If it exists, change in config should not cause the update to project just because file is open. The update happens to project only if it will be referencing config file or is changed for own config file
• tryFindDefaultConfiguredProjectAndLoadAncestorsForOpenScriptInfo finds, creates, or reloads the default project and ancestor tree (for find all project)
• tryFindDefaultConfiguredProjectForOpenScriptInfo finds, creates or reloads default project for the open file
• When finding orphan configured projects, instead of keeping ref and its login on configured project, we go through open files and all the default projects and projects seen for finding default project are retained. This ensures whatever situation, the "should the project be kept alive" answer never changes because of some updates missing or something like that.

[typescript-bot]

Looks like you're introducing a change to the public API surface area. If this includes breaking changes, please document them on our wiki's API Breaking Changes page.

Also, please make sure @DanielRosenwasser and @RyanCavanaugh are aware of the changes, just as a heads up.

[sheetalkamat]

This is exactly what happens when you open commonFile2 when it has tsconfig next to it that doesn't contain that file. This will be fixed to look for this project in #57196 but this makes the behavior consistent and not confuse when file belongs to right project or not .

[sheetalkamat]

This doesnt reschedule update for project if its already scheduled through set of updated projects

[sheetalkamat]

Earlier we use to skip if file was not part of inferred project, but change in configFile can have impact on whats the default project, so we upate the default config File Name for this file in cache and make sure that the project is present. Only if its new we schedule update otherwise the project doesnt need to be updated.