Fix expected dataset check in test runners

[jsoriano]

Data stream manifests can override the dataset, this is configured in the policy, but then when checking generated documents, it fails with:

[0] field "data_stream.dataset" should have value "beat.stats", it has "beats.stack_monitoring.stats"
[1] field "event.dataset" should have value "beat.stats", it has "beats.stack_monitoring.stats"

Seen in elastic/integrations#4708.

Also fix issue that was silently skipping static tests for input packages, because they were looking for the sample event in the wrong path.

[jsoriano]

I wonder why this was not detected by the test case we have for this.

We do this check only with format_version >= 2.0.0. I will fix the test case.

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-12-15T18:45:18.793+0000

• Duration: 34 min 14 sec

Test stats 🧪

Test	Results
Failed	0
Passed	870
Skipped	0
Total	870

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (34/34)	💚
Files	67.188% (86/128)	👍
Classes	61.957% (114/184)	👍
Methods	48.705% (376/772)	👎 -0.063
Lines	31.906% (3406/10675)	👎 -0.03
Conditionals	100.0% (0/0)	💚

[jsoriano]

Dataset checks are only executed for since 2.0.0.

[jsoriano]

/test

[mrodm]

LGTM!