[ Security Solution ] Fix Refetch logic with new timeline batching

[logeekal]

Summary

PR : #204034 fixed some issues with timeline batching. It was not able to fix one of the issue with Refetch logic which exists in main ( resulting in a flaky test ) and causing some tests to fail in 8.16, 8.17 and 8.x.

Issue Description

There are 2 issues with below video:

1. When user updates a status of an alert, the Refetch only happens on the first batch, which is an incorrect behaviour. We should fetch all the existing batches.

Before	After Fix
main_reftech_issue.mp4	fix_refetch_alert_status_change.mp4

3. When user clicks Refresh manually, then also only first batch is fetched, which should have rather fetched all the present batches.

Before	After fix
Main_refetch_refresh_issue.mp4	fix_refetch_refresh_issue.mp4

This is not a new issue and it existed before as well but this change in batching highlighted it.

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

• Unit or functional tests were updated or added to match the most common scenarios

[elasticmachine]

Pinging @elastic/security-threat-hunting-investigations (Team:Threat Hunting:Investigations)

[elasticmachine]

⏳ Build in-progress, with failures

• Buildkite Build
• Commit: d467844

Failed CI Steps

• Check Types