feat(snapshot): provide config to resolveSnapshotPath

[hi-ogawa]

Description

• closes resolveSnapshotPath to provide project root #6742

Currently call flow looks like this:

SnapshotState.create
  -> VitestNodeSnapshotEnvironment.resolvePath(path)
  -> RuntimeRPC.resolveSnapshotPath(path)
  -> SnapshotManager.resolvePath(path, context)
  -> SnapshotStateOptions.resolveSnapshotPath(path, extension, context)

Context is technically not snapshot package level concern, but in order to pass it through, I changed SnapshotManager. Probably there is a different way to achieve something similar without changing SnapshotManager, but I think this works for now. Bigger structural change would be required later anyways for #1620.

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	63ea057
🔍 Latest deploy log	https://app.netlify.com/sites/vitest-dev/deploys/67219a83a785410008e62915
😎 Deploy Preview	https://deploy-preview-6800--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]

Can we also expose a type from vitest/node? Maybe ResolveSnapshotPathHandler?

[sheremet-va]

feat(vitest,snapshot)

Can we keep a single scope? Several scopes just make it harder to parse release notes. "vitest" is kind of redundant. The scope is not about the package