Update Group by before Issues and PRs are fully loaded leads to incomplete fetch from GitHub repo

[SAN-MUYUN]

Describe the bug
When updating the Group by field before the Issues are PRs are fully loaded, WATcher seems to stop fetching the remaining Issues and PRs. Users are only able to view the Issues and PRs which are loaded before Group by field is updated. Clicking the Sync button does not reload the page.

To Reproduce
Steps to reproduce the behavior:

1. Choose a large repo (e.g., CATcher-org/WATcher) to load. The default Group by should be Assignee
2. While the page is still loading (progress spinner is still visible), update the Group by filter to Milestone
3. Observe that not all Issues/PRs are loaded.
4. Click on the Sync button on the top right corner, page does not reload. Missing PRs and Issues are still not loaded.

Expected behavior
It is expected that when updating Group by, WATcher continues to fetch all Issues/PRs. Or when Sync button is clicked, all Issues and PRs should be fetched correctly.

Screenshots
Change the Group by while WATcher is still loading Issues and PRs from GitHub (From Assignee to Milestone in this case)

WATcher stops fetching Issues and PRs from GitHub Repo, when there should be many of them to be fetched and displayed. Page remains the same when click the Sync button on the top right corner

Without changing anything filters, reload the whole page. Wait for all Issues and PRs to be loaded. All the Issues and PRs are displayed this time.

Desktop (please complete the following information):

• OS: Windows 11
• Chrome
• Version: 1.4.1

Additional context

1. This issue is not limited to updating Group by from Assignee to Milestone. Updating it from Milestone to Assignee will reproduce the same bug.
2. Sync button does not work might because of there is no change in the GitHub repo. Latest modified time is still the same, hence page reload is prevented