After calling refetchConnection in a pagination container cursor will not update.

After updating to 1.6.1 pagination is broken after calling refetchConnection.

When calling loadMore I pass in the endCursor as the cursor, but in my requests it gets passed as null.
If i refetch using a cursor then that cusor will persist for all subsequent loadMore requests.

This breaks our current implementation, and it's not clear using the documentation that anything has changed in this workflow.

Start by reproducing the issue in a pagination container using refetchConnection followed by loadMore, checking whether the endCursor is passed as null or whether a refetched cursor persists. Inspect the pagination-container flow and existing tests for refetchConnection and loadMore. Done means subsequent loadMore requests use the current endCursor after refetching.

Written by the indexing model from the issue text.