allow to see exports for non-enumerable properties (vercel#4783)

### Description

enumerate all properties for namespace object creation.

This follows the webpack logic

test cases in vercel/next.js#49106

allow to see exports for non-enumerable properties (vercel#4783)

### Description

enumerate all properties for namespace object creation.

This follows the webpack logic

test cases in vercel/next.js#49106

improve error handling (vercel#4779)

### Description

[return fallback metadata when image processing
fails](vercel@31c1557)
[improve error reporting for ecmascript parsing
errors](vercel@813852a)

### Testing Instructions

see vercel/next.js#49093

---------

Co-authored-by: Alex Kirszenberg <alex.kirszenberg@vercel.com>

Fix TSConfig extends pointing to node module (vercel#4772)

In vercel#4754, I screwed up the resolution logic for configs that reference
another config inside a node module. In it, I incorrectly joined
`/tsconfig.json` before performing any lookup, because I thought the
joining was happening in the `combinePaths` in
https://github.com/microsoft/TypeScript/blob/611a912d/src/compiler/commandLineParser.ts#L3315.
But, that combine has no real affect, it immediately gets stripped in a
call to `getDirectoryPath` in
https://github.com/microsoft/TypeScript/blob/611a912d/src/compiler/moduleNameResolver.ts#LL1703C93-L1703.

Instead, it performs a basic `node_module` lookup using the input module
name, and even tries to load the file referenced at that location (eg,
it's a `extends: 'foo/tsconfig.json'`). If that fails, then it combines
with an implied `/tsconfig` the same way a `/index` is appended when
doing `require('./directory')`.

Fixes WEB-974

Fix TSConfig extends pointing to node module (vercel#4772)

In vercel#4754, I screwed up the resolution logic for configs that reference
another config inside a node module. In it, I incorrectly joined
`/tsconfig.json` before performing any lookup, because I thought the
joining was happening in the `combinePaths` in
https://github.com/microsoft/TypeScript/blob/611a912d/src/compiler/commandLineParser.ts#L3315.
But, that combine has no real affect, it immediately gets stripped in a
call to `getDirectoryPath` in
https://github.com/microsoft/TypeScript/blob/611a912d/src/compiler/moduleNameResolver.ts#LL1703C93-L1703.

Instead, it performs a basic `node_module` lookup using the input module
name, and even tries to load the file referenced at that location (eg,
it's a `extends: 'foo/tsconfig.json'`). If that fails, then it combines
with an implied `/tsconfig` the same way a `/index` is appended when
doing `require('./directory')`.

Fixes WEB-974

Do not use interop logic on proxy modules (vercel#4761)

### Description

Proxy modules must not use interop logic, otherwise only the `default`
export works correctly

next.js PR: vercel/next.js#49033

More fluent GraphTraversal API (vercel#4598)

### Description

This PR refactors the API of `GraphTraversal` to be more fluent, and
less magical. It should make it easier to use and understand. Had this
in store from trying to debug a lifetime issue in another branch.

### Testing Instructions

Surface-level change.

Next.js PR: https://github.com/vercel/turbo/pulls/alexkirsz

chore: Update `swc_core` to `v0.75.41` (vercel#4756)

### Description

 - Fix WEB-969
 - Fix vercel#4747


### Testing Instructions

Look at CI of the next.js counterpart:
vercel/next.js#48982

chore: Update `swc_core` to `v0.75.41` (vercel#4756)

### Description

 - Fix WEB-969
 - Fix vercel#4747


### Testing Instructions

Look at CI of the next.js counterpart:
vercel/next.js#48982

Update 1-turbopack-bug-report.yml

Ask for Next.js version since there is no standalone Turbopack version yet.