fix(jest-config): add missing 'slash' dependency

[joshuakimDwan]

Summary

I updated my jest library to latest(27.3.1) and ran test. The following error occured:

Error: jest-config tried to access slash, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.

Required package: slash
Required by: jest-config@virtual:1bcce2f81654c62ba2c1f43389ad4059fbcc03a8875db1c4310173c058b718cab0f288f5cb8b498bea4c346752a90efbfc010d5498d6be71854ef8949f11199a#npm:27.3.1 (via /[my-directory]/.yarn/__virtual__/jest-config-virtual-d3c1205189/0/cache/jest-config-npm-27.3.1-8c4eee5f7f-1a86b03456.zip/node_modules/jest-config/build/)

I was trying to find the cause of this problem. The cause was that the code using 'slash' was committed last month (#11922) but the 'slash' dependency was not added to package.json.

So I solved this problem by adding the missing dependency.

[codecov-commenter]

Codecov Report

Merging #12078 (86dbdda) into main (7bb400c) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main   #12078   +/-   ##
=======================================
  Coverage   68.88%   68.89%           
=======================================
  Files         324      324           
  Lines       16669    16669           
  Branches     4814     4814           
=======================================
+ Hits        11483    11484    +1     
+ Misses       5153     5152    -1     
  Partials       33       33           

Impacted Files	Coverage Δ
packages/expect/src/utils.ts	96.37% <0.00%> (+0.51%)	⬆️

---

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 7bb400c...86dbdda. Read the comment docs.

[SimenB]

Thanks for the PR! Unfortunately I missed it and merged #12080 instead. Sorry about that!

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.