Feature: deterministic VITEST_WORKER_ID for each file

Clear and concise description of the problem

Would be awesome if we could have a deterministic assignment to VITEST_WORKER_ID.
At the moment each spec file runs in a random worker depending on some random events liek for example speed of other spec files before the current one.
For example I would like to initialize faker with unique seed per worker, like this:

faker.seed(11+Number(process.env.VITEST_WORKER_ID))

and if it is deterministic I can use snapshots with generated data and they will always match.

Suggested solution

calculate total number of workers(is this possible?), put all the spec files in array, sort them by created date and assign X to each worker.
This means that tests created first will always keep the VITEST_WORKER_ID 1, whereas all new tests will get the highest VITEST_WORKER_ID.

Alternative

No response

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Start by tracing how spec files are assigned to workers and how VITEST_WORKER_ID is set. Evaluate whether a stable assignment can account for the total worker count and file ordering, then verify that repeated runs give each file the same worker ID and support stable faker seeds.