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`?
const [count, updateCount] = useState('(empty)');
        useEffect(() => {
          Scheduler.unstable_yieldValue(`Schedule update [${props.count}]`);
          ReactNoop.flushSync(() => {
            updateCount(props.count);
          });
          
          expect(ReactNoop.getChildren()).not.toEqual([
            span('Count: ' + props.count),
          ]);
        }, [props.count]);
        return <Text text={'Count: ' + count} />;
      }
      expect(() =>
        act(() => {
          ReactNoop.render(<Counter count={0} />, () =>
            Scheduler.unstable_yieldValue('Sync effect'),
          );
          expect(Scheduler).toFlushAndYieldThrough([
            'Count: (empty)',
            'Sync effect',
          ]);
          expect(ReactNoop.getChildren()).toEqual([span('Count: (empty)')]);
        }),
      ).toErrorDev('flushSync was called from inside a lifecycle method');
      expect(ReactNoop.getChildren()).toEqual([span('Count: 0')]);
    });
    it('unmounts previous effect', () => {
      function Counter(props) {