…s global errors

A container that failed or aborted — typically a class whose @BeforeAll
threw or failed an assumption — used to be reported as an invented test
result. Such a result is counted in the run statistics, and its history
id is one no execution ever produces, so no retry could ever replace it.
The platform sends no events for the tests inside such a container, so
nothing can be backfilled either; the failure now becomes a run-level
GlobalError carrying the original exception.

A skipped subtree still backfills a skipped result for every test the
plan can name, with the identity it has in a real run. Test templates,
test factories and parameterized classes are containers whose
invocations only exist once they run: a skipped one has nothing to
report, and a result for the container itself would carry a history id
no invocation ever produces. Such containers are collected and reported
once as a run-level error instead.

With no non-test identifier reaching stopTest any more, the AS_ID=-1
marker that hid the invented results from the report goes too.

… errors

A @BeforeClass, @afterclass or @ClassRule that threw, or a @BeforeClass
assumption, used to vanish from the report entirely: JUnit 4 reports it
on the description of the class itself, with no events for the tests it
prevented, and the listener's update of a test it never started was a
silent no-op. The run looked green with fewer tests than expected. Such
a failure is now a run-level GlobalError naming the class, the count of
tests inside it and the cause. Nothing is backfilled: JUnit 4 does not
name the tests a class-level failure prevented, and the message claims
nothing about whether they ran, since a before and an after failure
arrive on the same description.

An invalid test class, or a Parameterized class whose parameters method
threw, is reported by JUnit 4 as a synthetic initializationError test.
That used to become a broken test result whose identity matches none of
the cases a green run produces, so no retry could replace it; it is
now a run-level error too.

A failed setupSpec used to be reported as an invented test result, and
every feature it prevented was backfilled as skipped — including
data-driven features, backfilled once with no parameters. The fixture
result is not a test case, and the parameterless feature result carries
a history id that no iteration ever produces: both are counted in the
run statistics under identities a green rerun cannot replace.

The failure now becomes a run-level GlobalError, with the broken fixture
kept in the spec scope. Plain features are still backfilled as skipped
with the identity they have in a real run. Data-driven features are not:
their iterations, and the values that tell them apart, only exist once
the feature runs, so they are named in the run-level error instead.

A failed cleanupSpec used to be visible only as a broken fixture inside
the spec scope; it is now a run-level error too, its features keeping
the results they already produced.