Add support for jsconfig/tsconfig paths in next/jest

[Naddiseo]

Describe the feature you'd like to request

I'm creating this to re-open #31159. The reproduction of the issue is still present in the with-jest example on the canary branch. If the "moduleNameMapper" section in jest.config.js is removed, jest won't find the "paths" field in tsconfig.json/jsconfig.json and is documented as such in both the example, and in the next testing documentation(ctrl+f "Optional: Absolute Imports and Module Path Aliases")

Describe the solution you'd like

next/jest should automatically fill the the "moduleNameMapper" field if paths if filled out in tsconfig.json.

Describe alternatives you've considered

There's the ts-paths package, and (as linked in #31159) the babel-plugin-module-resolver package. I used a home grown solution that's mostly lifted from the ts-jest