beforeEach return fn doesn't receive context that afterEach receives

[luixo]

Describe the bug

Consider code:
test1.spec.ts

import { test as originalTest } from 'vitest';

type Fixture = { foo: number };

const test = originalTest.extend<Fixture>({
  foo: async ({}, use) => {
    await use(1);
  },
});
beforeEach<Fixture>(({ foo })=> {
  console.log(`beforeEach ${foo}`);
});
afterEach<Fixture>(({ foo }) => {
  console.log(`afterEach ${foo}`);
});

In this case we'll get not data in beforeEach as expected, but afterEach can access the data.

beforeEach undefined
afterEach 1

Consider pretty similar case
test2.spec.ts

import { test as originalTest } from 'vitest';

type Fixture = { foo: number };

const test = originalTest.extend<Fixture>({
  foo: async ({}, use) => {
    await use(1);
  },
});
beforeEach<Fixture>(({ foo })=> {
  console.log(`beforeEach ${foo}`);
  return ({ foo: afterFoo }) => {
    console.log(`afterEach ${foo} / ${afterFoo}`);
  };
});

This code will throw on beforeEach callback (effectively an analogue to afterEach), I would expect to actually see:

beforeEach undefined
afterEach undefined / 1

Reproduction

See above

System Info

Not applicable

Used Package Manager

yarn

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[sheremet-va]

This looks like a bug, but I would expect it to work like test.beforeEach because you can define separate contexts at the top level