Make sure we have Agroal datasources before configuring health checks

[gsmet]

Fixes #43990

[gsmet]

@michalvavrik I tried to add a test to the quarkus-agroal-deployment module but I couldn't reproduce the issue. I'm not sure what you're doing to trigger it specifically. Do you have an idea of how we could reproduce it in the main repo?

[yrodiere]

LGTM, though I find it odd that the bean would not be resolvable... I suspect the bean having the default scope (dependent), toghether with the use of bytecode recorders, might have something to do with that, so I sent a suggestion to your fork: gsmet#193

[michalvavrik]

@michalvavrik I tried to add a test to the quarkus-agroal-deployment module but I couldn't reproduce the issue. I'm not sure what you're doing to trigger it specifically. Do you have an idea of how we could reproduce it in the main repo?

I tried, but inside Argoal deployment module you have a JDBC extension (H2) so I think you won't reproduce it there. If you drop it you can reproduce it like this 84813f9. So unless you have different module I don't think you can reproduce it.

[gsmet]

OK, I think we will have to live with it then. @michalvavrik if you can independently verify the last version of this PR fixes it for you, that would be awesome.

[michalvavrik]

I tried the latest version and it fixes my issue. Thank you

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit c9d008b.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.