Add test class progress logging on CI

[findinpath]

While going through the CI logs it can be helpful to pinpoint
the specific test class issuing errors on the logs.

Description

While going through the CI logs it can be helpful to pinpoint
the specific test class issuing errors on the logs.
If the JVM suddenly crashes while running the @BeforeClass setup methods, with the help of the current changes
it can be seen which specific class is causing these issue and reduce therefore the time needed to reproduce locally
the issue from the CI server.

Is this change a fix, improvement, new feature, refactoring, or other?

Improvement

Is this a change to the core query engine, a connector, client library, or the SPI interfaces? (be specific)

Testing infrastructure.

How would you describe this change to a non-technical end user or system administrator?

Pinpoint the test class causing JVM crashes while setting up the testing infrastructure for its test methods.

Look for:

• BEFORE CLASS
• AFTER CLASS

in the CI logs corresponding to the build of this PR.

Related issues, pull requests, and links

Documentation

(x) No documentation is needed.
( ) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.

Release notes

(x) No release notes entries required.
( ) Release notes entries required with the following suggested text:

[hashhar]

Hit #11634 - unrelated.