fix(jest-next.js): rectify broken jest moduleNameMapper configuration

[sabertazimi]

Rectify Jest configuration for renovate-bot #814 pull request.

close #815
issue vercel/next.js#35634
issue vercel/next.js#36312
issue vercel/next.js#36682

Pull Request

This PR Contains

• bugfix
• new feature
• code refactor
• test update
• typo fix
• metadata update

Motivation / Use-Case

Breaking Changes

Test-Case

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

Additional Info

[github-actions]

Lighthouse Report

✨ https://blog-5zwyhx63z-sabertaz.vercel.app/

🚀 Vercel preview deployment
⚡ Lighthouse report

Category	Score
🟢 performance	92
🟢 accessibility	100
🟢 best-practices	100
🟢 seo	100
🟢 pwa	100

✨ https://blog-5zwyhx63z-sabertaz.vercel.app/posts

🚀 Vercel preview deployment
⚡ Lighthouse report

Category	Score
🟢 performance	97
🟢 accessibility	100
🟢 best-practices	100
🟢 seo	100
🟢 pwa	100

✨ https://blog-5zwyhx63z-sabertaz.vercel.app/tags

🚀 Vercel preview deployment
⚡ Lighthouse report

Category	Score
🟢 performance	99
🟢 accessibility	100
🟢 best-practices	100
🟢 seo	100
🟢 pwa	100

✨ https://blog-5zwyhx63z-sabertaz.vercel.app/books

🚀 Vercel preview deployment
⚡ Lighthouse report

Category	Score
🟢 performance	98
🟢 accessibility	100
🟢 best-practices	100
🟢 seo	100
🟢 pwa	100

✨ https://blog-5zwyhx63z-sabertaz.vercel.app/about

🚀 Vercel preview deployment
⚡ Lighthouse report

Category	Score
🟢 performance	98
🟢 accessibility	100
🟢 best-practices	100
🟢 seo	100
🟢 pwa	100

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
blog	✅ Ready (Inspect)	Visit Preview	May 6, 2022 at 5:58PM (UTC)

[codecov]

Codecov Report

Merging #816 (1889eb6) into main (dd184a4) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #816   +/-   ##
=======================================
  Coverage   99.39%   99.39%           
=======================================
  Files         175      175           
  Lines         990      990           
  Branches       85       85           
=======================================
  Hits          984      984           
  Misses          5        5           
  Partials        1        1           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update dd184a4...1889eb6. Read the comment docs.

[pull-request-quantifier-deprecated]

This PR has 11 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +6 -5
Percentile : 4.4%

Total files changed: 1

Change summary by file extension:
.js : +6 -5

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detetcted.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.