fhir native compilation is eating up lot of memory

The native compilation of the camel-fhir extension is quite demanding in term of resources and the native-process easily reach 14GB of RSS (which is the hard coded limit the native-image can reach) which make not possible to test the fhir extension as examplle with GitHub Actions.

We should investigate how to optimize the build of the fhir extension

Start by reproducing native compilation for the camel-fhir extension and monitor the native-process RSS, especially in the GitHub Actions environment. Read the native-image build configuration and existing build logs to identify the resource-heavy step. Done means the FHIR native build uses less memory and can complete within the stated 14GB limit.

Written by the indexing model from the issue text.