Handle incompatible changes in patch releases

[mcollovati]

Hilla does not introduce breaking changes in patch releases, but since we have byte code manipulation and other usages of Hilla internal API, it may happen that a change in a patch release breaks the quarkus-hilla extension.

We should find a way to handle these changes to support both the olds and new Hilla patch releases.

An idea could be fixing the actual code base and adding methods or code blocks to handle the backward compatibility, marking it with the Hilla version that breaks the functionality (e.g. @CompatibilityFix("2.1.X")).
The annotations (or comments or whatever) could then be checked by the build process to prevent such workarounds to enter the next minor of quarkus-hilla,

We should also consider some build time solution to remove unnecessary code (see #285 (comment))