[BUG] Runtime dependency with Lombok APIs when using @SneakyThrows in combination with ECJ + Takari Lifecycle Plugin

[pjmartos]

Describe the bug
Lombok code leaks when using Takari Lifecycle + jdt compilerId (via ECJ) + @SneakyThrows, thus forcing the lombok artifact to be available at runtime.
Any other combinations lead to the correct code being generated:

• Maven Compiler Plugin + javac compilerId
• Maven Compiler Plugin + eclipse compilerId (via Plexus Compiler Eclipse)
• Takari Lifecycle + javac compilerId

To Reproduce

1. Clone https://github.com/pjmartos/lombok-takari-ecj-issue.git
2. Run mvn compile from the project's root folder
3. After decompiling the compiled class com.pmartos.App, we can see that the generated code has a runtime dependency with Lombok APIs:

        try {
            // code throwing an exception
        } catch (Throwable var2) {
            throw Lombok.sneakyThrow(var2);
        }

4. Run java -cp target/classes com.pmartos.App from the project's root folder (the POM is configured to use Java 21 but it should be possible to use Java 11+ if needed)
5. A ClassDefNotFoundError is returned; there shouldn't be such errors at runtime, but due to point 3 the error happens nonetheless.

In more elaborate applications for which an uber JAR or similar archive is built, the error will likely surface as soon as lombok has scope provided in the project's POM.

Expected behavior

1. The code does not fail and instead prints a message Successfully thrown and caught! Exception message: This is a test.
2. The generated code for class com.pmartos.App no longer has a runtime-dependency with Lombok APIs:

        try {
            // code throwing an exception
        } catch (Throwable var2) {
            throw var2;
        }

Version info

• Lombok 1.18.20 to 1.18.34
• Javac 21.0.3 (Oracle JDK)
• Javac 17.0.10 (Oracle JDK)
• Takari Lifecycle Plugin 2.1.5 to 2.2.0
• Eclipse ECJ 3.33.0 to 3.39.0 (Takari Lifecycle breaks with 3.39.0)

Additional context
None