[compiler] Fixture to show ref-in-render enforcement issue with useCallback

[mvitousek]

Stack from ghstack (oldest at bottom):

• [compiler] Make ref enforcement on by default #30716
• [compiler] Allow functions containing refs to be returned #30724
• [compiler] Reposition ref-in-render errors to the read location of .current #30723
• [compiler] Don't error on ref-in-render on StartMemoize #30715
• -> [compiler] Fixture to show ref-in-render enforcement issue with useCallback #30714
• [compiler] Exclude refs and ref values from having mutable ranges #30713

Test Plan:
Documents that useCallback calls interfere with it being ok for refs to escape as part of functions into jsx

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
react-compiler-playground	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 16, 2024 5:16pm

[josephsavona]

this case is interesting. we don't know when the prop will be called, so we probably should be permissive and allow it since the callback could be called during an event/effect