test: vitest prefer-each

[Shinigami92]

references #2098 (comment)

TODOs and Notes for myself

• we should check if we need to set the seed in a setup block, because it might be that the description title is not executed again
  • right now I assume the repeats might handle the faker instance differently than the previous for-loop, but I need to check that
• the global unique was/is repeated 🤔 how does it behave if the seed gets reset? does this affect the global store? did we fixed it now accidentally via faker instance store?

---

Helpful docs to understand the .each string syntax: https://vitest.dev/api/#test-each

For debugging purposes it can help quite a log to set reporters: 'verbose' in vitest config!

[codecov]

Codecov Report

Merging #2144 (1c97296) into next (06bc5af) will decrease coverage by 0.01%.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##             next    #2144      +/-   ##
==========================================
- Coverage   99.59%   99.59%   -0.01%     
==========================================
  Files        2607     2607              
  Lines      244977   244977              
  Branches     1148     1149       +1     
==========================================
- Hits       243997   243993       -4     
- Misses        953      957       +4     
  Partials       27       27              

see 2 files with indirect coverage changes

[Shinigami92]

@ST-DDT could you have a first look and re-evaluate if I did not made any mistakes?

[Shinigami92]

I'm now experimenting a bit with the repeats and it looks like that the "string" description title does not get executed again (as assumed).
So we need to move the seed() into a beforeAll or we need to use describe.each.
I think beforeAll is more clear (but sadly more verbose) here

[Shinigami92]

blocked by vitest-dev/vitest#3334

• repeats does not work at all vitest-dev/vitest#3334

we will use the "old" strategy for now