[Compiler Bug]: Compilation skipped, reason unclear

### What kind of issue is this? - [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization) - [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin) - [x] eslint-plugin-react-compiler (build issue installing or using the eslint plugin) - [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script) ### Link to repro https://playground.react.dev/#N4Igzg9grgTgxgUxALhAHQHZwhsAXAAgGEIBbABxwQ0IF4CAKASgNoD4DhMCDtdCAlngSkwrAgG00IAIbSANAWkAjaQF1M3Xjny8ZAG33KZcANbjmrDlww8eAgGaMHA-cJgIAJgElhogHT61ADmeAAWBBwADCw2dnYA9AkEACIQBJCkCOECGMFaPAC+WsUYWny6Lm4IHj5+YvRQYAgAsiIQDJbsnAUEHniwtkIiYCWKEsOiakyYhQDcmCDyIHwuwSggAhQQMIR4AJ7kCJwEAAr6UMG5APLkeAI6BIUEDjBkBADkxsoI+gC05AuVwwfw8Jjwf2wFFcNQSngE+A+CzKGAYcQISSh5FcMnuOBaEE8CGQSlkhmkswyuIRLgQYnOlxudweuCYcyW4DCEAA7t4aDUMAYwCgHEKEIUgA ### Repro steps The above example triggers `preserve-manual-memoization` when a callback references a memoized value declared later in the same component. If this behavior is intended, the error message could be clearer, as it is very hard to identify that the issue is caused by declaration order. Moving the callback after the useMemo will make the eslint compiler plugin happy again. ### How often does this bug happen? Every time ### What version of React are you using? latest ### What version of React Compiler are you using? latest