Document wrapping behavior of `TestExecutionListener` callbacks

[sbrannen]

Overview

The Javadoc for all "after" callback methods in TestContextManager (such as afterTestExecution()) states the following.

Note that listeners will be executed in the opposite order in which they were registered.

However, most developers would not logically think to read the Javadoc for TestContextManager when trying to reason about TestExecutionListener callbacks.

Therefore, as mentioned by @nizametdinovcrx in #34225 (comment), we should officially document the "wrapping behavior" of TestExecutionListener callbacks, especially with regard to the fact that "after" callbacks are invoked in reverse registration order.

Since I authored the documentation for JUnit Jupiter's Wrapping Behavior of Callbacks, I will likely borrow from that.

Related Issues

• Document order of callback methods and extensions that run after test/container execution junit-team/junit5#1620
• DirtiesContextTestExecutionListener has unexpected execution order leading to errors #34225