[Dataset quality] Show info about closed indices

[yngrdyn]

When we were fixing a bug for closed indices in #230943, some questions were raised but the main discussion would be:

Do we want to have some information regarding possible closed indices within dataset quality page or details?
Please bear in mind that, afaik, indices are closed explicitly by the user.

Concerns:

• Having an indicator associated to a dataStream regarding a closed backing index without actually checking if some documents within the selected time range are impacted could be ignored (e.g. a forever indicator)

[mohamedhamed-ahmed]

Thanks for following up on this @yngrdyn !!

I would actually like to know at first if the information of a closed index would be beneficial for the user when looking at the dataset quality page.

From my point of view the size of a specific data stream won't be reflecting the actual size if we don't take into account the closed indices, which might be a bit misleading to the user if they look at the page without a specific indicator that tells them this info.

If this is much work to be done through a closed index we can at least show the user an indicator mentioning that in this selected time range there is a number of closed indices and that these numbers they see aren't taken into consideration.

[LucaWintergerst]

I don't think that there is too much we can do here. We can't know if the closed index contains data that's important or in the time range the user is looking at. It's also kind of rare to have a closed index. You would only have them if you actually closed them yourself. We can assume for now that if a user does this, that they are on their own and would be able to open them again.

To me this feels like it's part of a broader set of functionality that would be better covered by things like auto-ops

[yngrdyn]

You would only have them if you actually closed them yourself.

Agree here, for me the action is explicitly done by the user.

If no objections I'll then proceed to close this discussion
@LucaWintergerst, @mohamedhamed-ahmed, @gbamparop