chore: fix snapshot of testng

[LingyuCoder]

Summary

Checklist

• Tests updated (or not required).
• Documentation updated (or not required).

[LingyuCoder]

!test-ng

[netlify]

✅ Deploy Preview for rspack canceled.

Name	Link
🔨 Latest commit	ebdde12
🔍 Latest deploy log	https://app.netlify.com/sites/rspack/deploys/6625fa8a151a3200080c43b2

[github-actions]

🟢🟢🟢 Test new runner successed

Task: https://github.com/web-infra-dev/rspack/actions/runs/8779158231

> monorepo@0.6.2 test:ng /home/webinfra/ec2-linux-ci-5/_work/rspack/rspack
> pnpm --filter "@rspack/test-tools" test:ng "--no-colors" "--silent=true" "--force-exit"

npm/darwin-arm64                         |  WARN  Unsupported platform: wanted: {"cpu":["arm64"],"os":["darwin"],"libc":["any"]} (current: {"os":"linux","cpu":"x64","libc":"glibc"})
npm/darwin-x64                           |  WARN  Unsupported platform: wanted: {"cpu":["x64"],"os":["darwin"],"libc":["any"]} (current: {"os":"linux","cpu":"x64","libc":"glibc"})
npm/win32-x64-msvc                       |  WARN  Unsupported platform: wanted: {"cpu":["x64"],"os":["win32"],"libc":["any"]} (current: {"os":"linux","cpu":"x64","libc":"glibc"})

> @rspack/test-tools@0.6.2 test:ng /home/webinfra/ec2-linux-ci-5/_work/rspack/rspack/packages/rspack-test-tools
> cross-env SNAPSHOT=legacy NO_COLOR=1 node --expose-gc --max-old-space-size=8192 --experimental-vm-modules ../../node_modules/jest-cli/bin/jest --logHeapUsage --config ./jest.config.legacy.js "--no-colors" "--silent=true" "--force-exit"

jest-haste-map: Haste module naming collision: example-basic
  The following files share their name; please adjust your hasteImpl:
    * <rootDir>/tests/treeShakingCases/cjs-tree-shaking-basic/package.json
    * <rootDir>/tests/treeShakingCases/reexport-all-as-multi-level-nested/package.json

PASS tests/Diagnostics.test.js (72 MB heap size)
PASS tests/HashTestCases.test.js (71 MB heap size)
PASS tests/StatsTestCases.basictest.js (96 MB heap size)
PASS tests/WatchTestCases.longtest.js (5.421 s, 70 MB heap size)
PASS tests/TestCasesNormal.basictest.js (13.565 s, 100 MB heap size)
PASS tests/HotTestCasesWeb.test.js (19.041 s, 92 MB heap size)
PASS tests/HotTestCasesWebWorker.test.js (19.592 s, 90 MB heap size)
(node:28576) ExperimentalWarning: VM Modules is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
PASS tests/HotTestCasesNode.test.js (20.239 s, 89 MB heap size)
PASS tests/HotTestStepWeb.test.js (21.988 s, 130 MB heap size)
PASS tests/ConfigTestCases.basictest.js (64.999 s, 407 MB heap size)
A worker process has failed to exit gracefully and has been force exited. This is likely caused by tests leaking due to improper teardown. Try running with --detectOpenHandles to find leaks. Active timers can also cause this, ensure that .unref() was called on them.

Test Suites: 10 passed, 10 total
Tests:       9 skipped, 2559 passed, 2568 total
Snapshots:   58 passed, 58 total
Time:        66.104 s
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?
Test new runner successed