Make streams test compatible with chicken test

[flash1293]

Make sure the logs stream works with the mapped = "unmapped" parameter. This isn't the case right now because all other data streams are captured by the default logs-*-* mappings, but logs is not.

[flash1293]

@gbanasiak This fails unit tests because you can't run with and without mapped=unmapped on the same cluster. The next test is cleaning up for the previous, but the test with mapped=unmapped will be aware of a different set of templates.

However, it would be nice to test it somehow - what I can think of is to move it to the very first position, but that's definitely brittle. Do you have a better idea?

I didn't test this, but I wonder whether we even need to exclude all the individual per-dataset templates for the unmapped test, instead of just bumping up the priority in ./templates/composable/logs-dynamic-false.json so it will overrule all the others...

[flash1293]

Testing this with 9e56387

[flash1293]

Kind of obvious in hindsight, but this has the same issue in the other direction... Not sure what the least hacky solution for this would be - any thoughts, @gbanasiak ?

[gbanasiak]

The next test is cleaning up for the previous, but the test with mapped=unmapped will be aware of a different set of templates.

facepalm! Of course... Well, we can move tests that absolutely require it to a new ES cluster. Let me add it here.

[gbanasiak]

LGTM

[esbenchmachine]

@flash1293
A backport is pending for this PR. Please add all required vX.Y version labels.

• If it is intended for the current Elasticsearch release version, apply the corresponding version label.
• If it also supports past released versions, add those labels too.
• If it only targets a future version, wait until that version label exists and then add it.
  (Each rally-tracks version label is created during the feature freeze of a new Elasticsearch branch).

Backporting entails:

1. Ensure the correct version labels exist in this PR.
2. Ensure backport PRs have backport label and are passing tests.
3. Merge backport PRs (you can approve yourself and enable auto-merge).
4. Remove backport pending label from this PR once all backport PRs are merged.

Thank you!