Avoid reifing Agroal configuration too early

[gsmet]

In OracleAgroalConnectionConfigurer, we are reifing the Agroal config and we shouldn't do it at this stage.
We need to check the properties directly and thus we add them to AgroalConnectionConfigurer. I kept the old method for now but it will be removed at some point in the future.

Fixes #44687

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit 4367b5f.

✅ 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.

Warning

There are other workflow runs running, you probably need to wait for their status before merging.

[github-actions]

🎊 PR Preview a3ce841 has been successfully built and deployed to https://quarkus-pr-main-44688-preview.surge.sh/version/main/guides/

• Images of blog posts older than 3 months are not available.
• Newsletters older than 3 months are not available.

[quarkus-bot]

Status for workflow Quarkus CI

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

✅ 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.

[yrodiere]

LGTM.

Though I must admit I wonder why this object cannot be accessed twice. Shouldn't the recorder that produces it, or even Quarkus' bytecode recorder system itself, cache the produced instance?

[gsmet]

Yeah so the FooConfigSupplier of Agroal are basically builders that you can build only once.

In this case, we were building the config so that we would have a getter to get the properties as the builder doesn't have getters (which makes sense).

So really, we were bending the API.