[UA] Guide user towards reindexing before manual resolution

[sebelga]

When testing #119441 I realised that we could leverage the reindex functionality that we have in place in UA to lower the number of manual resolutions that we display to the user.

We can see here that for the same index we get 2 critical deprecation:

If I open the second one first I see

How exactly do I fix this? It is not quite clear. And there is no indication that our reindexing will solve this for the user, so actually he should not worry about it.

Possible solution

• We could detect the deprecations for indices and verify if the reindex takes care of it. In such case we could filter out the deprecations that the reindex will take care of. This would be the best UX as we would reduce by 50% or more the number of deprecation in the table when entering UA.
• As an alternative, in a first iteration, we could simply change the copy and guide the user to first reindex all the indices (the copy would only show if there are indices to reindex and other deprecations with manual resolution). We would then automatically refresh the table after each reindex is done and the deprecations solved by reindexing would be removed from the table.

[elasticmachine]

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