[Metrics UI] Fix OR logic on redundant groupBy detection

[Zacqary]

Summary

Fixes #116195

In this PR, host.name will still be flagged as redundant in this case:

But with these changes, it will NOT be flagged in this case:

[elasticmachine]

Pinging @elastic/infra-monitoring-ui (Team:Infra Monitoring UI)

[Zacqary]

Another issue I just noticed is that I don't think agent.hostname should be flagged in this case:

Fixing this might be a more complicated change, though, so I wonder if we should scope it to a later PR.

Not sure how common a query like this would even be.

[kibanamachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 54e79ce
• Storybooks Preview

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
infra	928.9KB	928.9KB	+56.0B

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[neptunian]

I wonder if instead of trying to validate their inputs we can make it more generic and anytime they are filtering on a field that is also being grouped there can be a generic warning message that they may get unexpected results and then link to some documentation explaining how and why with some examples. Even if they are using an OR like in the issue #116195, it seems still valid to notify them that they'd get less results than may be expected.

[Zacqary]

@neptunian Yeah that approach makes more sense. I can see about writing up some docs for this and redo this PR.