Make the `enableSchedulingProfiler` flag dynamic for the profiling build (so marks can be disabled). I think it should be sufficient to do something like:
```js
export const enableSchedulingProfiler =
  __PROFILE__ && dynamicFeatureFlags.enableSchedulingProfiler;
```

Update our User Timing API check to include `clearMeasures` and when we call `mark(name)`, also call `clearMeasures(name)` to avoid clogging the entries buffer. (Apparently this has a significant negative performance impact for Firefox.)
state = {didRender: false};
      render() {
        if (this.state.didRender === false) {
          this.setState({didRender: true});
        }
        return null;
      }
    }
    ReactTestRenderer.create(<Example />, {unstable_isConcurrent: true});
    expect(marks).toEqual([
      `--react-init-${ReactVersion}`,
      '--schedule-render-512',
    ]);
    marks.splice(0);
    expect(() => {
      expect(Scheduler).toFlushUntilNextPaint([]);
    }).toErrorDev('Cannot update during an existing state transition');
    gate(({old}) =>
      old
        ? expect(marks).toContain('--schedule-state-update-1024-Example')
        : expect(marks).toContain('--schedule-state-update-512-Example'),
    );
  });
  
  it('should mark render phase force updates for class component', () => {
    class Example extends React.Component {