Fix false positive for self-referential useCallback

[KimHyeongRae0]

Fixes #35576.

The immutability rule currently reports a TDZ-style error for a stable self-reference inside useCallback, such as removing the same callback from an event listener.

This updates hoisted context tracking to only record real reads that happen before initialization. Self-references introduced by the callback being memoized are ignored, while later captures that actually read a declaration before initialization still fail.

Tests:

• add a regression that allows a self-referential useCallback
• keep a regression that still rejects a later declaration capture
• run yarn workspace eslint-plugin-react-hooks test --runInBand

[liufang88789-ui]

This is a tricky one to get right. The distinction between a stable self-reference (callback capturing itself through memoization) and a genuine TDZ violation is subtle, and the old code couldn't tell them apart.

The approach works well - by tracking which captures are introduced by the memoization itself versus which are genuine out-of-order reads, you avoid the false positive while keeping the real TDZ check intact.

The two regression tests are the right cases: removing itself is exactly the stable self-reference pattern that should be allowed, and reading before is declared is a legitimate error that should still be caught. Good coverage.