Ignore matching data streams if include_data_streams is false

[danhermann]

Currently, any requests that match a data stream on APIs that are not enabled for data streams return an error that a data stream was matched. This PR changes the name resolution to simply ignore data streams for APIs that are not enabled for data streams.

Relates to #53100

Relates to #57712

[martijnvg]

LGTM

[martijnvg]

This fails when this yaml test is executed with security enabled.
logs-* is expanded to logs-foobar and then later this fails with a 404.

So in order to make this test execute constantly with and without security enabled, we should change
index: logs-* to `index: logs-foobar. This should change the meaning of this test.

[danhermann]

Thanks for pointing that out. It seems unfortunate that behavior can differ when security is enabled even when it is not restricting access to any of the items in the test. E.g., close logs-* succeeds without security but fails with security enabled even though the user has access to both the logs-foobar data stream and logs-foobarbaz index. I suppose that difference in behavior already exists with indices and aliases, though.

[martijnvg]

Yes, that subtle difference in behaviour also exists with indices and aliases.

[elasticmachine]

Pinging @elastic/es-core-features (:Core/Features/Data streams)

[danhermann]

This is likely to be abandoned in favor of #58154. Leaving it open only until that can be confirmed.

This PR depends on #58154

[danhermann]

@elasticmachine update branch

[elasticmachine]

merge conflict between base and head

[danhermann]

@elasticmachine run elasticsearch-ci/2