fix: compiler.webpack.ModuleFilenameHelpers type error

[jerrykingxyz]

Summary

Example:
Input:

module.exports  = xxx;

Ouput: (NodeNext)

Object.defineProperty(exports, "__esModule", { value: true }); // this seems a bug of ts compiler, which need further investigation
module.exports = xxx;
// console undefined

Output: (CommonJS)

module.exports = xxx;

Test Plan

Require Documentation?

• No
• Yes, the corresponding rspack-website PR is __

[jerrykingxyz]

!eco-ci

[rspack-bot]

📝 Ran ecosystem CI: Open

suite	result
modernjs	❌ failure
nx	✅ success
rspress	✅ success
rsbuild	❌ failure
compat	✅ success

[jerrykingxyz]

!eco-ci

[rspack-bot]

📝 Ran ecosystem CI: Open

suite	result
modernjs	✅ success
nx	✅ success
rspress	✅ success
rsbuild	✅ success
compat	✅ success

[hardfist]

@xiaoxiangmoe it's indeed caused by nodeNext, let revert temporarily and dig into it later

[hardfist]

let's merge it

[SoonIter]

@jerrykingxyz how can i test whether this bug is fixed in latest Typescript version "5.5.3"
#7211

[jerrykingxyz]

@SoonIter

1. checkout this PR and replace module to NodeNext
2. try access compiler.webpack.ModuleFilenameHelper and it will throw a type error
3. upgrade the ts version and access compiler.webpack.ModuleFilenameHelper again

[SoonIter]

I think this issue is caused by const ModuleFilenameHelpers = exports;

this is a surprising writing of cjs code ... I think it has been fixed by renaming to .ts file