Improve lazy instrumentation mechanism

[eupp]

As an optimization, we currently use lazy instrumentation logic to re-transform only those classes related to the test.
This lazy instrumentation mechanism utilizes the fact that managed strategy can intercept object initialization, reads/writes of fields, and other related events, to invoke class bytecode transformation at certain points, mimicking the semantics of Java class initialization:
https://docs.oracle.com/javase/specs/jls/se23/html/jls-12.html#jls-12.4

However, there several bugs and problems currently with this feature. Because of these bugs we sometimes have to use hacks to trigger eager transformation of classes, see examples:

• isThreadContainerClass
• isCoroutineDispatcherInternalClass

Under this issue we aim to fix these problems.

Implementation:

• Ensure JLS-12.4 semantics is properly implemented.
• Ensure constructors are properly handled (relevant issue Unify bytecode transformation logic for constructors (<init> methods) and regular methods. #449).
• Implement a work-around for code run in ignored sections.

Testing:

• Implement infrastructure for fine-grained unit tests to check what classes are instrumented during the test.
• Add unit tests to check that JLS-12.4 semantics is covered.
• Add unit tests to check interaction with ignored sections mechanism.