[compiler] Allow ref access in callbacks passed to event handler props

[jasonyuezhang]

Summary

Fixes facebook#35040. The React compiler incorrectly flags ref access within event handlers as ref access at render time. For example, this code would fail to compile with error "Cannot access refs during render":

  const onSubmit = async (data) => {
    const file = ref.current?.toFile(); // Incorrectly flagged as error
  };

  <form onSubmit={handleSubmit(onSubmit)}>

This is a false positive because any built-in DOM event handler is guaranteed not to run at render time. This PR only supports built-in event handlers because there are no guarantees that user-made event handlers will not run at render time.

How did you test this change?

I created 4 test fixtures which validate this change:

• allow-ref-access-in-event-handler-wrapper.tsx - Sync handler test input
• allow-ref-access-in-event-handler-wrapper.expect.md - Sync handler expected output
• allow-ref-access-in-async-event-handler-wrapper.tsx - Async handler test input
• allow-ref-access-in-async-event-handler-wrapper.expect.md - Async handler expected output

All linters and test suites also pass.

---

Copied from facebook#35062
Original PR: facebook#35062

[macroscopeapp]

Allow functions that access refs to be passed to built-in DOM event handler props while still rejecting direct ref values in ValidateNoRefAccessInRender.validateNoRefAccessInRenderImpl

Add identifier tracking for onX props on built-in tags, compute isUsedAsEventHandler, and adjust operand validation to call validateNoDirectRefValueAccess but skip validateNoRefPassedToFunction when used as a built-in event handler prop. Update fixtures to cover allowed and error cases, and normalize Promise instances in React Hooks inspection tests.

📍Where to Start

Start in the validator at validateNoRefAccessInRenderImpl in ValidateNoRefAccessInRender.ts.

---

Macroscope summarized b0665d7.