Ensure declaration reference published paths

[eps1lon]

We currently emit declaration for files that reference unknown modules e.g. export { default as GlobalError } from 'VAR_MODULE_GLOBAL_ERROR'; in next/dist/build/templates/app-page.d.ts.

Since the referenced modules are declarated in compiled.d.ts which we do publish, I see no reason to not also let next/dist/build/templates/app-page.d.ts reference the appropriate ambient declaration file (compiled.d.ts).

The alternative is marking the whole module as @internal but checking if every export truly never flows into a public module takes way more time.

This also unblocks the TypeScript 5.4 upgrade in #64043. TS 5.4 would emit a declaration referencing the appropriate ambient declaration but since compiled.d.ts is not part of the program but misc.d.ts is, the declaration would reference misc.d.ts(/// <reference path="../../../types/misc.d.ts") which is not published and would cause TypeScript compilation to fail.

Closes NEXT-3104

[eps1lon]

All of the removed modules are already declared in compiled.d.ts

[eps1lon]

This doesn't work. We have some modules that have more specific types internally because we have the types available as a dependency (e.g. Webpack). When published, the Webpack dependency is stripped and replaced with a looser definition based on what we assume is actually emitted. I don't think TypeScript supports this pattern outside of @internal annotations.

compiled.d.ts isn't even referenced by any emitted declaration at the moment while the non-published misc.d.ts is.

Need to dig deeper why some declarations are emitted in the first place.