feat(runner): provide test context to test.each

[hi-ogawa]

Description

• Closes Provide test context to test.each() #4642

I made a few prototypes here in this PR based on the suggestions in the issue.

todo

• finalize api (Now this PR includes only each7)
  • last argument? issuecomment-1871372078
    • see test.each5 and test.each7
    • currently fixture extraction looks for first argument, so it needs to adjust getUsedProps slightly, but it should be simple.
    • the usage of spreading (...args, { expect }) => ... is not possible, but overall, this feels least breaking and least surprising in terms of API.
  • first argument? issuecomment-1859974766
    • see test.each6
    • based on context's usage, the user needs to switch between ({ expect }, arg) => ... and (arg) => ..., which might be un-intuitive than having it in the last argument. Also, if Vitest would change the default to be { context: true } in the future, then all users (regardless of context/fixture usage) would be impacted by breaking change. Also this would break Jest compatibility.
  • inside test context object? issuecomment-1894155135
    • see test.each3
    • the downside would be similar to "first argument" explained above. But if ever, breaking change is possible, then this API feels best with Vitest's context concept.
  • where to boolean flag?
    • test.each([...])("title", (...) => { ... }, { context: true }) issuecomment-1894155135
      
      • see test.each7
    • test.each([...], { context: true }) issuecomment-1859974766
      • see test.each5
      • it cannot support string literal usage test.each`${0} | ${1}`
• ts function overload
• support TestOption.context at the 2nd position feat(vitest): "test" accepts options object as the second parameter #5142
• test + type testing
• docs

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

• Run the tests with pnpm test:ci.

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

[netlify]

✅ Deploy Preview for fastidious-cascaron-4ded94 canceled.

Name	Link
🔨 Latest commit	c6eae14
🔍 Latest deploy log	https://app.netlify.com/sites/fastidious-cascaron-4ded94/deploys/65cac8aa1e10050008ef26ea

[hi-ogawa]

each in ExtendedAPI (here) and SuiteAPI (below) seems to be redundant.