Use TestExecutionListener to log test start and end in org.eclipse.ui.tests

[trancexpress]

Tests in org.eclipse.ui.tests use org.eclipse.ui.tests.harness.util.TestRunLogUtil.LOG_TESTRUN to log/print when a test started and ended. This is a JUnit 4 rule which is present in some but not all tests. E.g. for #4009, QuickAccessDialogTest doesn't have this rule and is a JUnit 5 test.

To add such log information for QuickAccessDialogTest, following the same pattern, we would have to define a JUnit 5 extension and add it to QuickAccessDialogTest.

We can instead do better and use org.junit.platform.launcher.TestExecutionListener to print start and end for all tests, not just JUnit 4 ones using LOG_TESTRUN. We would need to remove LOG_TESTRUN from the tests, to avoid double printing.

For an example of how to use TestExecutionListener, see e.g.: eclipse-jdt/eclipse.jdt.ui@accc76e

[HeikoKlare]

The logging for test start/end via TestRunLogUtil was also done via the JUnit 4 CloseTestWindowsRule for many Platform UI tests. This logging was removed when migrating to JUnit 5 using the CloseTestWindowsExtension. I already asked here #4009 (comment) if that removal during migration was intended as it makes the identification of test execution order for debugging purposes quite difficult, but Lars didn't respond to my questions in that discussion.

I like the proposal of using an TestExecutionListener. That sounds like an even more reasonable approach than defining another extension for the logging that then needs to be attached to every test class.