Following up on https://github.com/reactjs/reactjs.org/pull/4486#discussion_r834319756 (/cc @acdlite )

React version: 18.0.0-rc.3-next-1159ff619-20220324

## Steps To Reproduce

1. schedule an update (e.g. `setState`) from within `useInsertionEffect` 


Link to code example: https://codesandbox.io/s/naughty-bogdan-boghf6?file=/src/index.js


## The current behavior

Update is applied and no warning is issued.

## The expected behavior

According to https://github.com/reactjs/reactjs.org/pull/4486/files#diff-a1c8ec10dc40c86b4bbd55ad3f0126835bd45e9aa9e56c846a2e28ad6dd6acffR602 `useInsertionEffect` cannot schedule updates. But `setState` seems to "work". Maybe this is just incidental because it's the first render?

I got the impression that this should definitely cause a warning (not implemented) but I wonder if we also should consistently drop updates from `useInsertionEffect`?
expect(Scheduler).toHaveYielded(['Render count: 0']);
    expect(ReactNoop).toMatchRenderedOutput('0');
    act(() => {
      
      setDisabled(false);
    });
    expect(Scheduler).toHaveYielded([
      'Render disabled: false',
      'Render count: 0',
    ]);
    expect(ReactNoop).toMatchRenderedOutput('0');
  });
  it('useReducer applies potential no-op changes if made relevant by other updates in the batch', () => {
    let setDisabled;
    let increment;
    function Counter({disabled}) {
      const [count, dispatch] = useReducer((state, action) => {
        if (disabled) {
          return state;
        }
        if (action.type === 'increment') {
          return state + 1;
        }
        return state;
      }, 0);
      increment = () => dispatch({type: 'increment'});
      Scheduler.unstable_yieldValue('Render count: ' + count);
      return count;
    }
    function App() {