[Bug]: mockImplementationOnce bleeds into withImplementation

[mysteryven]

Version

29.4.2

Steps to reproduce

1. Open online repo
2. Run npm install
3. Run npm test

Expected behavior

 const mock = jest
    .fn(() => 'outside callback')
    .mockImplementationOnce(() => 'once');

  mock.withImplementation(
    () => 'inside callback',
    () => {
      expect(mock()).toBe('inside callback');
    }
  );

  expect(mock()).toBe('once');
  expect(mock()).toBe('outside callback');

Actual behavior

 const mock = jest
    .fn(() => 'outside callback')
    .mockImplementationOnce(() => 'once');

  mock.withImplementation(
    () => 'inside callback',
    () => {
       mock() // 'once'
    }
  );

  mock() // 'outside callback'
  mock() // 'outside callback'

Additional context

I think it is a little counterintuitive when unused implementationOnce bleeds into withImplementation.

Environment

System:
    OS: macOS 13.0.1
    CPU: (8) arm64 Apple M1 Pro
  Binaries:
    Node: 18.12.1 - ~/.nvm/versions/node/v18.12.1/bin/node
    Yarn: 1.22.4 - ~/.yarn/bin/yarn
    npm: 8.19.2 - ~/.nvm/versions/node/v18.12.1/bin/npm
  npmPackages:
    jest: ^29.4.2 => 29.4.2

[SimenB]

https://github.com/facebook/jest/releases/tag/v29.4.3

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.