4.x - Dbclient Integration Tests Fixed

[Tomas-Kraus]

Some changes in HealthCheck API caused build issues with integration tests. Also name removal from HealthCheckResponse caused test failures.

Fixed build issues mostly with import changes.
HealthCheck name was checked as part of response. Changed this to verify name directly from HealthCheck instance.

[Tomas-Kraus]

[INFO] Results:
[INFO] 
[INFO] Tests run: 141, Failures: 0, Errors: 0, Skipped: 0
[INFO] 
[INFO] 
[INFO] --- maven-failsafe-plugin:3.0.0-M5:integration-test (destroy) @ helidon-tests-integration-dbclient-jdbc ---
[INFO] Integration Tests: DB Client Common ................ SUCCESS [  1.930 s]
[INFO] Integration Tests: DB Client JDBC .................. SUCCESS [ 14.109 s]

[INFO] Results:
[INFO] 
[INFO] Tests run: 158, Failures: 0, Errors: 0, Skipped: 0
[INFO] 
[INFO] --- maven-failsafe-plugin:3.0.0-M5:verify (test) @ helidon-tests-integration-dbclient-appl ---
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------

[Tomas-Kraus]

@romain-grecourt Those tests are quite unstable. This changeset can't affect anything and they are still failing.

[Tomas-Kraus]

@romain-grecourt I added one more changeset to run Db Client tests with H2 DB during regular -Ptests profile run.
This should avoid at least build and some simple use-case regressions in tests.

[Tomas-Kraus]

@romain-grecourt I had to rewrite tests initialization for appl tests here. It was not working properly with in memory DBs.
Also updated imports to match format pattern from Tomas L. and changed logger to use System.

[Tomas-Kraus]

Code should look much better now. I went trough everything to fix bad coding style.

[tomas-langer]

LGTM