feat: support modern useEffectEvent

[nwidynski]

This PR adds compatibility for React's new useEffectEvent hook, with fallback to our legacy shim.

✅ Pull Request Checklist:

• Included link to corresponding React Spectrum GitHub Issue.
• Added/updated unit tests and storybook for this change (for new code or code which already has tests).
• Filled out test instructions.
• Updated documentation (if it already exists for this component).
• Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

🧢 Your Project:

[snowystinger]

Thanks for the PR

[snowystinger]

I'm not really sure why fn was optional.... this is an internal hook for us (not documented), so I think we should probably have it be required, then we can get rid of this extra noop function

[snowystinger]

Doh, I see we were passing it possibly undefined in utils/src/useEvent.ts, but we should apply your noop specifically there i think. Looks like that hook very specifically allowed for it.
Sorry for the extra noise and thank you. Happy to handle any other transformations as a result of my request if you don't have time.

[nwidynski]

@snowystinger I'm fine with requiring the argument, but wanted to note that we definitely lose some convenience. With the upgrade to rules-of-hooks you recently performed, the recommended pattern to opt out of reactivity is to wrap callbacks passed via props with useEffectEvent. Often times props are optional, which would require us to provide a noop, making this pretty cumbersome.

[snowystinger]

@snowystinger I'm fine with requiring the argument, but wanted to note that we definitely loose some convenience. With the upgrade to rules-of-hooks you recently performed, the recommended pattern to opt out of reactivity is to wrap callbacks passed via props with useEffectEvent. Often times props are optional, which would require us to provide a noop, making this pretty cumbersome.

Yeah, I see that, though it looks like we've only needed it in one place out of all of our usages. So I'm ok with it, we'll see what the rest of the team thinks.

Thanks again!