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 current = root.current;
  current.lanes = lane;
  markRootUpdated(root, lane, eventTime);
  ensureRootIsScheduled(root, eventTime);
}
 This is split into a separate function so we can mark a fiber with pending
 work without treating it as a typical update that originates from an event;
 e.g. retrying a Suspense boundary isn't an update, but it does schedule work
 on a fiber.
function markUpdateLaneFromFiberToRoot(
  sourceFiber: Fiber,
  lane: Lane,
): FiberRoot | null {
   
  sourceFiber.lanes = mergeLanes(sourceFiber.lanes, lane);
  let alternate = sourceFiber.alternate;
  if (alternate !== null) {
    alternate.lanes = mergeLanes(alternate.lanes, lane);
  }
  if (__DEV__) {
    if (
      alternate === null &&
      (sourceFiber.flags & (Placement | Hydrating)) !== NoFlags
    ) {
      warnAboutUpdateOnNotYetMountedFiberInDEV(sourceFiber);