fix(jest-each, @jest/globals): allow passing ReadonlyArray type of a table to describe.each and test.each

[mrazauskas]

Fixes #12294.

Summary

As it is mentioned in the issue, typings of describe.each and test.each throw an error if a tuple with const assertion is passed as a table, e.g. describe.each([['foo'], ['bar']] as const).

Unexpected for me, but simply replacing Array with ReadonlyArray in typings solves this issue. The const assertion turns an array literal into a readonly tuple. That’s why ReadonlyArray works here.

Does ReadonlyArray fit in jest-each code? It did not compile without changes, now TS is happy. Logic did not change. So perhaps that’s alright?

Test plan

Type test are added and extended.

[codecov-commenter]

Codecov Report

Merging #12297 (ad72e3c) into main (71c1e93) will decrease coverage by 0.22%.
The diff coverage is 0.00%.

❗ Current head ad72e3c differs from pull request most recent head c93c704. Consider uploading reports for the commit c93c704 to get more accurate results

@@            Coverage Diff             @@
##             main   #12297      +/-   ##
==========================================
- Coverage   67.53%   67.31%   -0.23%     
==========================================
  Files         328      328              
  Lines       17241    17297      +56     
  Branches     5065     5065              
==========================================
- Hits        11644    11643       -1     
- Misses       5564     5621      +57     
  Partials       33       33              

Impacted Files	Coverage Δ
packages/jest-each/src/bind.ts	100.00% <ø> (ø)
packages/jest-types/__typechecks__/globals.test.ts	0.00% <0.00%> (ø)
packages/expect/src/utils.ts	96.09% <0.00%> (-0.49%)	⬇️

---

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 71c1e93...c93c704. Read the comment docs.

[SimenB]

Perfect, thank you!

[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.