[DevTools] Hook names are correctly extracted when parsing nested hook calls (#22037)

## Summary This commit fixes an issue where DevTools would currently not correctly extract the hook names for a hook call when the hook call was nested under *another* hook call, e.g.: ```javascript function Component() { const InnerComponent = useMemo(() => () => { const [state, setState] = useState(0); return state; }); return null; }; ``` Although it seems pretty rare to encounter this case in actual product code, DevTools wasn't handling it correctly: **Expected Names:** - `InnerComponent` for the `useMemo()` call. - `state` for the `useState()` call. **Actual** - `InnerComponent` for the `useMemo()` call. - `InnerComponent` for the `useState()` call. The reason that we were extracting the name for the nested hook call incorrectly is that the `checkNodeLocation` function (which attempts to check if the location of the hook matches the location in the original source code), was too "lenient" and would return a match even if the start lines of the locations didn't match. Specifically, for our example, it would consider that the location of the outer hook call "matched" the location of the inner hook call (even though they were on different lines), and would then return the wrong hook name. ### Fix The fix in this commit is to update the `checkNodeLocation` function to more strictly check for matching start lines. The assumption here is that if 2 locations are on different starting lines, they can't possibly correspond to the same hook call. ## Test Plan - yarn flow - Tests still pass - yarn test - yarn test-build-devtools - new regression tests added - named hooks still work on manual test of browser extension on a few different apps (code sandbox, create-react-app, internally).