Fix: @catch on fragment root breaks usePaginationFragment and usePrefetchableForwardPaginationFragment

[christiansany]

Problem

When @catch is applied to the root of a fragment used with usePaginationFragment, hasNext always returned false even when the response included pageInfo.hasNextPage: true. @catch on a child field worked correctly — only the root-level case was broken.

Root cause

When @catch is on the fragment root, the compiler sets metadata.catchTo: "RESULT" on the ReaderFragment. At read time, RelayReader._catchErrors wraps the entire fragment data in a Result envelope:

{ok: true, value: {friends: ..., id: ...}}
// or
{ok: false, errors: [...]}

The pagination/refetch hook internals were reading fields directly off fragmentData and never unwrapping this envelope:

• getConnectionState did getValueAtPath(fragmentData, ["friends"]) → undefined → returned {cursor: null, hasMore: false} → hasNext === false.
• useLoadMoreFunction and useRefetchableFragmentInternal did fragmentData[identifierField] → undefined → broken refetch identifier.

Fix

Added a tiny helper getFragmentInternalData(fragmentNode, fragmentData) that unwraps the Result envelope when catchTo === 'RESULT' (no-op otherwise). Applied it at every internal call site that reads from fragmentData. The user-facing data returned from usePaginationFragment remains wrapped, matching the generated Result<T, unknown> type.