Background

While investigating issue #7833, I noticed some differences between what contributors are told to run locally vs what CI runs, and I'd like to understand the intended workflow.

Current State

• CI runs: nextest-release, and other tests commands based on nextest.
• Contributing docs recommend: make test (cargo test based) - see Development Environment docs
• Available options: Both cargo test and nextest variants exist in Makefile

Questions

1. What should contributors run locally? Should we be using the nextest commands that match CI, or are the cargo test commands preferred for local development?

2. Are both needed? Are there specific use cases where the cargo test versions are preferred over nextest?

3. Documentation update needed? Should the contributing guide be updated to clarify which commands to use when?

Context

This came up because I hit a test failure with make test that doesn't occur in CI, leading to some confusion about the expected local workflow.

Related: #7833