Use minimal endings when generating declarations for js

[weswigham]

Fixes #34624

Fun fact! This was mostly fixed with the addition of the bundledPackageName flag. All that was missing was passing in an option to our specifier generator for (bundled) js declaration emit. The declaration file we generate (when you add "bundledPackageName": "mylib") now looks like

declare module "mylib/versions.static" {
    var _default: {
        "@a/b": string;
        "@a/c": string;
    };
    export default _default;
}
declare module "mylib" {
    export { versions };
    import versions from "mylib/versions.static";
}

[sandersn]

Maybe this is easier to read? But maybe not, I just wanted to write it out for comparison.

Suggested change

	{ importModuleSpecifierPreference: isBundle ? "non-relative" : "relative", importModuleSpecifierEnding: isBundle ? "minimal" : undefined },
	isBundle ? { importModuleSpecifierPreference: "non-relative", importModuleSpecifierEnding: "minimal" } : { importModuleSpecifierPreference: "relative" },

[weswigham]

Eh, I think I prefer having the single object literal, even if the condition happens to be the same for both fields.