Consistently use "wrap semantics" for started/finished and opened/closed listener methods

[marcphilipp]

• Call TestExecutionListener finish methods in reverse order
• Call EngineExecutionListener.executionFinished method in reverse order
• Call LauncherDiscoveryListener.class finish methods in reverse order
• Call LauncherSessionListener closed method in reverse order
• Reuse CollectionUtils.forEachInReverseOrder
• Optimize common cases

Resolves #3082.

---

I hereby agree to the terms of the JUnit Contributor License Agreement.

---

Definition of Done

• There are no TODOs left in the code
• Method preconditions are checked and documented in the method's Javadoc
• Coding conventions (e.g. for logging) have been followed
• Change is covered by automated tests including corner cases, errors, and exception handling
• Public API has Javadoc and @API annotations
• Change is documented in the User Guide and Release Notes
• All continuous integration builds pass