[Bug]: globalSetup doesn't process moduleNameMappers

[cope]

Version

29.7.0

Steps to reproduce

	moduleNameMapper: {
		'@/(.*)': ['<rootDir>/src/$1'],
		'test/(.*)': ['<rootDir>/test/$1']
	},
	globalSetup: '<rootDir>/test/_setup/setupTests.ts',

In setupTests.ts just import anything from source using '@/...' and it will fail with: Error: Jest: Got error running globalSetup - Cannot find module.

Moving setupTests.ts to setupFiles does not break.
But I do not want to run it before each and every test.

Expected behavior

Expected to work.

Actual behavior

Fails with: Error: Jest: Got error running globalSetup - Cannot find module.

Additional context

Duplicate of #6179, but @wanton7 solution just caused more weird issues to deal with.

I tried replacing the shortcut import with a full one, which loads the first file, but then fails within that one... so I would have to change many files to remove short imports which is a pain.

Environment

System:
    OS: Windows 10 10.0.19045
    CPU: (16) x64 Intel(R) Core(TM) i7-10875H CPU @ 2.30GHz
  Binaries:
    Node: 22.0.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.22 - C:\Program Files\nodejs\yarn.CMD
    npm: 10.5.1 - C:\Program Files\nodejs\npm.CMD
    pnpm: 9.0.6 - C:\Program Files\nodejs\pnpm.CMD
  npmPackages:
    jest: ^29.7.0 => 29.7.0

[benasher44]

Dup of #11644