Inconsistent sort behavior within grouped subrows after unsort.

[tearingItUp786]

Describe the bug (required)
If you have a table that supports grouping + sorting, the unsorted state of the subrows is different depending on which columns you toggle sorting on.

Provide an example via Codesandbox! (required)
the example to reproduce the issue.

Steps To Reproduce (required)
Steps to reproduce the behavior:

1. Go to sandbox
2. Create a mental snapshot of how the subrows are ordered for "test" group.
3. Click on the text inside of the "Last Name" column (be sure not to accidentally toggle grouping) until you have moved from sort ascending, sort descending, unsorted. You should have to click a total of 3 times.
4. See error; the unsorted state of the "test" groups subrow should not match what you saw in step 2.

Expected behavior (Recommended)
The unsorted state of the subrows for a group should be consistent.

Screenshots
Will get these to you if there's any issues with my instructions!

Desktop (please complete the following information):

• OS: MacOS Version 10.13.6 (17G14042)
• Browser: Chrome
• Version 88.0.4324.96 (Official Build) (x86_64)

Additional context
Add any other context about the problem here.

[dgattey]

Also encountering this problem - after unsorting, this is the state of my subRows, 100% reversed from what it starts out as:

I don't have grouping on, but I have useGlobalFilter/useFilters/useSortBy on

[github-actions]

This issue is being marked as stale (no activity in the last 14 days)

[github-actions]

This issue has been detected as stale and automatically closed. It's very likely that your issue has remained here this long because it would require breaking changes to v7. React Table v8 is currently in alpha (soon beta!) and already contains bug fixes, performance improvements and architectural changes that likely address this issue.

• If your v7 issue has been previously labeled as requiring breaking changes, please try the new v8 alpha/beta releases
• If your v7 issue has not already been labeled as a breaking change, open a new issue.
• If this was a v8 issue and was closed by mistake, please reopen or leave a comment below.