[Index Patterns] Better alias handling

[afharo]

Describe the feature:
When creating an Index Pattern, Kibana automatically adds the trailing * as the user starts typing.

Ideally, Kibana should show a warning when the index pattern matches both: aliases and indices. Or it could even stop the automatic addition of the * if the name matches an alias (allowing the user to explicitly add it, though).

Describe a specific use case for the feature:
This could cause unexpected behaviours in data models where the alias points to the latest-most-recent index, but the user keeps the old indices for recovery purposes.

i.e.:

1. The user has the index my-index-001 containing all the documents, and the alias my-index is pointing to my-index-001.
2. The user needs a reindex (i.e.: due to a mappings update) and they create my-index-002. When the reindex is done, they point the alias to the new index, but they don't delete my-index-001 just in case they need to rollback.

When the index pattern is my-index*, it returns duplicated results until the old index is removed. IMO, Kibana should make it more obvious to the the user that this may occur when including an alias and an index in the same index-pattern.

What do you think?

[elasticmachine]

Pinging @elastic/kibana-app-services (Team:AppServices)

[mattkime]

@afharo How common is this case? Do any of the solutions make this likely?

I think we need to do a better job communicating which indices are matched by a data view - #72665 - but its unclear to me if its worthwhile to modify the UI for creating index pattern strings.

[ppisljar]

Thank you for contributing to this issue, however, we are closing this issue due to inactivity as part of a backlog grooming effort. If you believe this feature/bug should still be considered, please reopen with a comment.