Log test aborted/skipped exceptions at INFO level in the TestContext framework

[sbrannen]

Overview

Currently, any time an aborted/skipped exception is thrown by a TestExecutionListener, the TestContextManager unconditionally logs the exception at WARN level -- or ERROR level for prepareTestInstance() callbacks.

For the latter, an aborted/skipped exception is certainly not an ERROR, and in general the associated log output is very verbose (including a stack trace) and not something the user should be warned about it.

To improve the user experience, we should therefore log such exceptions at INFO level.

Test aborted/skipped exceptions

• JUnit Jupiter: org.opentest4j.TestAbortedException
• JUnit 4 org.junit.AssumptionViolatedException
• TestNG: org.testng.SkipException

Related Issues

• Introduce support for aborting JUnit 4 and TestNG tests in AOT runtime #31478

[sbrannen]

Reopening to ensure that GraalVM reflection hints are registered for skipped exception types.