chore(ci): Add GraalVM E2E tests and GH workflows

[phipag]

Summary

This PR introduces E2E tests for testing against native images deployed on AL2023.provided runtime compiled using GraalVM.

It is important to have these tests to cover regressions of future code changes. For example, if the GraalVM metadata files were not updated inline with new code changes. We want to protect customers from releasing changes that break GraalVM compatibility.

Tests pass ✅

• https://github.com/aws-powertools/powertools-lambda-java/actions/runs/16373230793

Changes

The GraalVM E2E tests are triggered by a custom e2e-graal maven profile which sets a System Property graalvm.enabled = true. This will be read within the E2E infrastructure logic to decide whether to deploy a native image on the Lambda provided runtime or not. The E2E test assertions themselves stay untouched because we expect the exact same output for native images like for JVM based Lambda handlers. We can include more utilities in GraalVM E2E tests as we grow the GraalVM support across more Powertools utilities by updating this maven profile configuration.

 <configuration>
      <skipAfterFailureCount>1</skipAfterFailureCount>
      <includes>
          <!-- Add additional E2E tests here when adding new GraalVM support to utilities. -->
          <include>**/MetricsE2ET.java</include>
          <include>**/LoggingE2ET.java</include>
          <include>**/ParametersE2ET.java</include>
      </includes>
      <excludes>
          <exclude>**/TracingE2ET.java</exclude>
      </excludes>
      <systemPropertyVariables>
          <graalvm.enabled>true</graalvm.enabled>
      </systemPropertyVariables>
  </configuration>

• Update GitHub action workflow to include e2e-graal job running the same Java matrix and same workflows like e2e
• Update E2E test handlers to include GraalVM metadata files required to run as native image (this will be same experience like an end user would do when deploying a Lambda handler)
• Update Infrastructure configuration to be compatible with GraalVM
  • Introduced new DockerConfiguration.java to hold configuration for CDK Bundling within Docker. Required for x86 cross-compilation of native image.

Issue number: #1803

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[phipag]

I don't understand why the osv-scanner fails since this vulnerability was not introduced by this PR. According to the docs it should only scan the PR diff. https://google.github.io/osv-scanner/github-action/#scan-on-pull-request

[leandrodamascena]

Hey @phipag great job! Some few comments to address before we merge it.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
2 Accepted issues

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

See analysis details on SonarQube Cloud

[phipag]

Thanks for your feedback @leandrodamascena, I addressed your comments.

[leandrodamascena]

Thanks for addressing all the comments @phipag! Ship it!

Approved!