Break build cycle between OTel, logging and Flyway

[geoand]

• Fixes: Conflicting open telemetry and flyway dependencies #45130

[geoand]

The issue with this one is that I have no idea what problem @Consume(LoggingSetupBuildItem.class) solved.
It was introduced in 72a983f but I don't see an example of what prompted its inclusion.

[quarkus-bot]

Status for workflow Quarkus CI

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

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

[geoand]

An alternative fix would be to check if the bean has been initialized and if not queue the records and it does become available to emit them all.
This solution however would require an API for checking whether a synthetic bean has been initialized. See this for more details.

[gsmet]

Yeah I also had a quick look yesterday and this is similar to another issue we had a few weeks back.

I'm a bit worried about just dropping @stuartwdouglas 's fix. Also a bit worried in general as this cycle is something that could happen quite a lot.

[geoand]

I'm a bit worried about just dropping @stuartwdouglas 's fix

Me too, but I don't have a way of knowing what problem it was meant to fix

Also a bit worried in general as this cycle is something that could happen quite a lot.

I think this specific instance is pretty unique as creating LogHandlerBuildItem is not terribly common among extensions

[gsmet]

OK, I suppose we will have reports soon enough if it's still needed.