feat: allow array element for test.each/for title formatting

[hi-ogawa]

Description

• Closes Add %_ format to skip a parameter in test.each/for #7511

This would be a bit of breaking change since $0, $1, ... weren't replaced previously.

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 vitest-dev ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	4350fbc
🔍 Latest deploy log	https://app.netlify.com/sites/vitest-dev/deploys/67b671fef17454000808c929
😎 Deploy Preview	https://deploy-preview-7522--vitest-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[sheremet-va]

This would be a bit of breaking change since $0, $1, ... weren't replaced previously.

I don't think anyone used it like this before in a static string. It also doesn't affect any functionality except displaying a name. Doesn't look like a breaking change to me

[hi-ogawa]

Okay, I had some concerns with edge cases, but I handled in the least breaking way, so let's go as minor.