Forward port away from deprecated React.ElementRef to React.ComponentRef

[mikehardy]

Summary:

React v19 deprecated React.ElementRef and recommends using React.ComponentRef

This appears to work just fine, with no other changes other than the type, with the exception of the Codegen phase which makes no allowance for ComponentRef during parsing

I altered the typescript and flow parsers to accept the new ComponentRef as well as the old ElementRef

• Fixes Codegen strictly requires deprecated React.ElementRef vs recommended React.ComponentRef #54272

Changelog:

[INTERNAL][DEPRECATED] - use React.ComponentRef in codegen in place of React.ElementRef

Test Plan:

This is mostly checked in jest tests, I updated the fixtures to send ComponentRef through, and I updated the snapshots to expect a message that indicates either ElementRef or ComponentRef are expected

[mikehardy]

There was a linting error in my diff, I fixed that and re-pushed.

The android build error is some deprecation warnings while -Werror is passed, not part of this PR

[cipolleschi]

Thanks @mikehardy for fixing this!

[meta-codesync]

@cipolleschi has imported this pull request. If you are a Meta employee, you can view this in D85556329.

[javache]

I believe the ComponentRef changes are specific to TypeScript, so no code under flow should be changed. Flow does not have a React.ComponentRef https://flow.org/en/docs/react/types/

[mikehardy]

@javache oh interesting! I am unfamiliar with flow types and assumed they would be similar, I'll focus this change on typescript when I get a chance / removing the flow bits then and re-push. Thanks for catching that

[mikehardy]

Okay, @cipolleschi - after Pieter's astute observation that this should be typescript-only since Flow does not have a corresponding change, I have re-pushed this with changes only to the typescript codegen parser + test fixtures + test snapshots. I believe that means you need to reimport?