Update only changed type baseline

This test is written in an invalid configuration that issues a program error: `--module esnext --moduleResolution nodenext`. The baseline shows that previously, the type of a default import was influenced by the `moduleResolution` setting. With the current change, the `moduleResolution` setting affects only module resolution, and the types of imports in `--module esnext` are now consistent across all `moduleResolution` settings. A future commit will revert this baseline change by *intentionally* using `impliedNodeFormat` information in `--module esnext`, but the current change gets us to a more rational starting point for making those substantive changes. Since `--moduleResolution nodenext` has been an error when not paired with `--module nodenext` for many versions now, the fact that this baseline is changing is not particularly meaningful for users.

Author: andrewbranch

tests/baselines/reference/moduleExportNonStructured.types

@@ -2,22 +2,22 @@
 
 === index.mts ===
 import * as exportAny from "./exportAny.cjs";
->exportAny : { default: any; }
+>exportAny : any
 
 import * as exportUnknown from "./exportUnknown.cjs";
->exportUnknown : { default: unknown; }
+>exportUnknown : unknown
 
 import * as exportSymbol from "./exportSymbol.cjs";
->exportSymbol : { default: symbol; }
+>exportSymbol : symbol
 
 import type * as exportAnyType from "./exportAny.cjs";
->exportAnyType : { default: any; }
+>exportAnyType : any
 
 import type * as exportUnknownType from "./exportUnknown.cjs";
->exportUnknownType : { default: unknown; }
+>exportUnknownType : unknown
 
 import type * as exportSymbolType from "./exportSymbol.cjs";
->exportSymbolType : { default: symbol; }
+>exportSymbolType : symbol
 
 === exportAny.d.cts ===
 declare const __: any;