[Watcher] Staleness in UI after ack'ing a firing rule

[jloleysens]

Kibana version:

Master 23edb41739

Describe the bug:

When a configured watcher alert starts firing and is ack'ed through the UI, navigating between the "Execution History" and "Action statuses" tabs after ack'ing leaves the UI reporting "firing" even though the configured alert was just ack'ed.

Steps to reproduce:

1. Run elastic + kibana on a non-basic license (e.g., trial yarn es snapshot --license trial)
2. Create a watch via the watcher UI in the ES management section. Configure it to check as quickly as possible (once every minute) and set a low threshold on an existing value like "updated_at".
3. Ack the watcher rule once it starts firing
4. Navigate to the "Execution history" tab
5. Navigate to the "Action statuses" tab
6. You should (incorrectly) be able to ack the watch again. Refreshing the page updates watcher action status..

Expected behavior:

Ack'ing a watch should update the UI even after navigating away (i.e., shouldn't require page reload to update).

Screenshots (if relevant):

Any additional context:

Any fixes to this should preferably happen only after #50908 is merged.

[elasticmachine]

Pinging @elastic/es-ui (Team:Elasticsearch UI)

[cjcenizal]

Possible dupe of #27758

[alisonelizabeth]

I think this is different from #27758.

In the last step, it's mentioned that refreshing the page resolves the problem.

You should (incorrectly) be able to ack the watch again. Refreshing the page updates watcher action status..

[elasticmachine]

Pinging @elastic/kibana-management (Team:Kibana Management)