Change quarkus-cache config phase from BUILD_TIME to RUN_TIME

[gwenneg]

Fixes #29934.

This PR changes the entire quarkus-cache config phase from BUILD_TIME to RUN_TIME. To make that possible, I had to refactor the bytecode recording a bit and move its execution time from STATIC_INIT to RUNTIME_INIT.

[gwenneg]

I wonder if that change is worth mentioning in the release note.

[gwenneg]

The native build failure is related, I'm fixing it.

[gwenneg]

ℹ️ I'm aware of the native build issue, I'll try to fix it tomorrow.

[geoand]

information_source I'm aware of the native build issue, I'll try to fix it tomorrow.

Any luck with this?

[gwenneg]

@geoand Sorry for the delay. I pushed a few changes, the native issue should be fixed now.

[geoand]

Nice, thanks!

[geoand]

Sorry, I closed it by accident...

[gwenneg]

@geoand Do you think this PR and/or #30005 should be mentioned in the community release note (the blog post)?

[geoand]

I think both should be mentioned as they are related, so I added the proper label - that leaves you on the hook to provide a small blurb which @gsmet can use in the release announcement :)

[geoand]

Copying from #29934 (comment):

The quarkus-cache config will be settable at run time starting Quarkus 2.16.0. It will also be possible to change some of the cache config values in real time (without restarting the app) using the programmatic API. Here's a preview of the cache doc from 2.16 that explains how to do that.