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 counter = React.createRef(null);
    ReactNoop.render(<Counter label="Count" ref={counter} />);
    expect(Scheduler).toFlushAndYield(['Count: 0']);
    expect(ReactNoop.getChildren()).toEqual([span('Count: 0')]);
    
    act(() => {
      if (gate(flags => flags.enableSyncDefaultUpdates)) {
        React.startTransition(() => {
          counter.current.updateCount(1);
          counter.current.updateCount(count => count + 10);
        });
      } else {
        counter.current.updateCount(1);
        counter.current.updateCount(count => count + 10);
      }
      
      expect(Scheduler).toFlushAndYieldThrough(['Count: 11']);
      expect(ReactNoop.getChildren()).toEqual([span('Count: 0')]);
      
      ReactNoop.flushSync(() => {
        ReactNoop.render(<Counter label="Total" />);
      });
      expect(Scheduler).toHaveYielded(['Total: 0']);
      
      expect(Scheduler).toFlushAndYield(['Total: 11']);
      expect(ReactNoop.getChildren()).toEqual([span('Total: 11')]);
    });
  });
  it('throws inside class components', () => {
    class BadCounter extends React.Component {