feat(crac): Support CRaC and priming of powertools tracing

[Attyuttam]

Summary

Changes

Added CRaC support in powertools-tracing, following the guide and blogs mentioned on the ticket.
Added automatic priming for powertools-metrics by preloading all the required classes, the list of classes is fetched from the JVM at compile time.

Issue number: #2004

---

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]

Hey @Attyuttam,

do you think you are able to develop inside Windows Subsytem for Linux (https://code.visualstudio.com/docs/remote/wsl) or inside a Docker container (https://code.visualstudio.com/docs/devcontainers/containers) or on a linux remote machine (https://code.visualstudio.com/docs/remote/remote-overview)?

As a quick solution, you could also make the changes locally and then build and run the tests inside a Docker container with Java and Maven installed.

What do you think?

A large amount of changes you made in this PR are related to your OS (Windows) and break our Linux-based CI. Making all tests OS-independent would be task on its own.

[Attyuttam]

sure @phipag , I will test as you suggested. Thanks !

[Attyuttam]

Hi @phipag , I’ve updated the changes and validated them in a Linux environment using WSL to match the project’s CI setup.
Please let me know if any further adjustments are needed.

[phipag]

Hey @Attyuttam,

this looks very good. Just a minor comment below and two small points:

1. Can you add a unit test that asserts no exception is thrown in before and after checkpoint? Similar to this: https://github.com/aws-powertools/powertools-lambda-java/pull/2081/changes#diff-70c782dbf1e2b25496c60c4098cf6a9eb6985384319fdba0940bc9129add124b
2. Let's add a no-op method such as init() to TracingUtils just so that users can reference TracingUtils without being forced to perform a changing operation such as adding an annotation. And after adding this, just make a small update in the documentation referencing init() instead of putAnnotation().

public static void init() {
    // Placeholder method used to enable SnapStart priming. Users need a direct reference to this class in order for the CRaC hooks to execute.
}

[Attyuttam]

Thanks for the comments @phipag. I have incorporated them.

[phipag]

Hey @Attyuttam,

this looks good now. Thanks! One last thing: You can see that the CI for GraalVM native is failing. The reason for this is that the Mockito inline mock maker is not supported for native unit tests and it fails now since you added mockito as a dependency.

To fix this, can you please add the subclass mock maker as a dependency for both GraalVM maven profiles in the pom.xml? Here is an example for this from the metrics module:

powertools-lambda-java/powertools-metrics/pom.xml

Lines 179 to 185 in 54fe0be

	<dependencies>
	<dependency>
	<groupId>org.mockito</groupId>
	<artifactId>mockito-subclass</artifactId>
	<scope>test</scope>
	</dependency>
	</dependencies>

powertools-lambda-java/powertools-metrics/pom.xml

Lines 153 to 159 in 54fe0be

	<dependencies>
	<dependency>
	<groupId>org.mockito</groupId>
	<artifactId>mockito-subclass</artifactId>
	<scope>test</scope>
	</dependency>
	</dependencies>

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
1 Accepted issue

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

See analysis details on SonarQube Cloud

[phipag]

Awesome work @Attyuttam, I just tested this and it works. Thanks for your contribution! I am looking forward to your future PRs on the issues assigned to you. As always, let me know if you have any questions. 🥳