Related to #237771.

When a background search is first created, it has some information about the state of the application when it was created to be used when restoring. However we rely on the search requests being polled & server-side behavior to update the saved object with the information about the search requests.

It is possible that the search requests are not polled (e.g. if the browser is closed or if in another tab the search requests are canceled) and don't get added to the saved object, which results in a background search saved object that has 0 search requests. Currently this is treated as if the background search is still in-progress, and thus displays a loading spinner indefinitely:

This is how it looks when inspecting the Background search:

The background search saved object should only contain 0 search requests for a few seconds & never an extended period of time, and thus should be treated as an error state rather than in-progress (if it has been more than a few seconds since the saved object was created).