Comprehensive GraalVM support for all utilities

[phipag]

Is your feature request related to a problem? Please describe.
We want to make it easy for customers to adopt Powertools and use or keep using GraalVM in v2 of the library.

Describe the solution you'd like
In #764, we provided GraalVM support for the Core Utilities (Logging, Metrics, Tracing). This issue tracks adding GraalVM support for all other utilities.

Progress

• Parameters: feat(v2): GraalVM support for Parameters utility #1833 (pending review)
• Idempotency: feat(v2): GraalVM support for Idempotency utility #1834
• Large Messages: feat(v2): GraalVM support for Large Messages utility #1835
• Batch Processing: feat(v2): GraalVM support for Batch Processing utility #1836
• Validation: feat(v2): GraalVM support for Validation utility #1837
• Custom Resources: feat(v2): GraalVM support for Custom Resources utility #1838
• Serialization Utils: feat(v2): GraalVM support for Serialization utility #1839

Additional context
We have a guide for adding GraalVM support to a utility: https://github.com/aws-powertools/powertools-lambda-java/blob/7f604e4c67d838d6f72ad340c5f4af7492f1e624/GraalVM.md

[jreijn]

I'll try and see if I can implement this for parameters. I've been using v1 with GraalVM and have some custom reflect-config.json files that I would like to get rid of :-)

[phipag]

Hey @jreijn,

this is awesome to hear! I saw your PR and will review it this week.

I also updated the initial issue description with a comprehensive list of all utilities and the progress made.

[phipag]

Hi @jreijn,

not to confuse you. I created sub-issues for better tracking. The one for the Parameters module is here: #1833

Let's move conversation to the sub-issue in case something comes up.

[jreijn]

That's a great improvement. Once the parameters modules if done I will try to pick up one of the other ones.