(cherry picked from commit f8686f1)

…ts (#5839)

With the introduction of the `SuiteSummaryGeneratingListener` the
dynamic tests were not included in the test discovery count leading to
an `NoTestsDiscoveredException` when suites contained only dynamic
tests. Counting the registration of dynamic tests in addition to the
directly discovered test solves this.

We did have a test case to cover this. While it checked that the tests
in the suite were executed, it did not check if the suite container
itself passed.

Checking this was actually surprisingly difficult.The
`EventConditions.container(DynamicSuite.class)` can be satisfied by the
events from the `DynamicSuite` and the `DynamicTestsTestCase`, so there
always exists some ambiguity about which event is being matched. By
matching exactly against the suite descriptor segment we can avoid
this.

(cherry picked from commit 7e7183f)

(cherry picked from commit cc110a6)

(cherry picked from commit 762d5aa)

(cherry picked from commit 3cce604)

The output directory is only needed for the
`passesOutputDirectoryCreatorToEnginesInSuite`, but because that test
uses the `SelectClassesSuite` every other test also needed to set the
output directory. This makes the tests larger than strictly necessary.

By removing the `TestReporter` from the `SingleTestTestCase` and adding
a dedicated  `SingleTestWithTestReporterTestCase` we can make all the
suite tests a bit more focused.