Remove build time initialisation of user metadata for GraalVM

[graemerocher]

Seems with strict image heap it is not safe to initialise anything that could represent user code. Previously we could get away with initialising our generated classes, but since this reference user classes the viral nature of build time init results in initialising user code.

This manifested in dev builds failing with an error on the LogLevel enum, I attempted to mark this is build time init but there are 2 problems with this:

1. It means any user defined enum will need to be marked as build time init
2. Once fixed I hit another problem with expression language expressions which also need to be build time initialised. These are again user defined and we cannot know what the are.

So unfortunately the only solution I see going forward is to completely remove the build time init or our generated metadata. This change does this and in local benchmarks does not seem to have a major impact on memory or startup, however does increase the image size by 2mb.

Fixes #10630

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[dstepanov]

We have some issues with enums values when the class is not on the classpath, I was thinking we can replace enums instance values with string or do try-catch aproach like classes.

[sdelamo]

@dstepanov what enums where you thinking of?