Fix implied formats, file watching, new source file creating during edits

[sheetalkamat]

This change includes:

1. When program is created, we track package.json per file that affect its implied format
2. We watch those files to invalidate resolutions of that file
3. If oldSourceFile.impliedNodeFormat is not same as new one, we need to create new file, so we pass that information to host
4. Document registry handles implied node format as part of its key to get the file and release it
5. Package.json files are being watched so we know when to clear the package json info cache.
6. Fixed issue with module resolution cache not passed around in watch mode
7. If implied file format is determined by package.json persence/absence and file is module, its reported with --explainFiles

Fixes #50086

[sheetalkamat]

@typescript-bot pack this

[typescript-bot]

Heya @sheetalkamat, I've started to run the tarball bundle task on this PR at 73f56b2. You can monitor the build here.

[typescript-bot]

Hey @sheetalkamat, I've packed this into an installable tgz. You can install it for testing by referencing it in your package.json like so:

{
    "devDependencies": {
        "typescript": "https://typescript.visualstudio.com/cf7ac146-d525-443c-b23c-0d58337efebc/_apis/build/builds/130808/artifacts?artifactName=tgz&fileId=0F60CBFC416351EB284A80B475F3B3683C765BFED326AB1F53DC657615AB3D2202&fileName=/typescript-4.8.0-insiders.20220730.tgz"
    }
}

and then running npm install.

---

There is also a playground for this build and an npm module you can use via "typescript": "npm:@typescript-deploys/pr-build@4.8.0-pr-50098-2".;

[weswigham]

Should both of these have a branch for when the file extension sets the format, for .cts, .cjs, .mjs and .mts files?

[sheetalkamat]

@DanielRosenwasser and myself discussed offline before this change and decided try this with only spitting this out when package.json determines the context.