Consider excluding all non-project classes from instrumentation

[shanshin]

At the moment, by default, the IntelliJ agent instruments all classes loaded into the JVM. In some cases, this causes the generation of an erroneous bytecode and a subsequent verification error (for example in #89).

In new versions of libraries, if the java compiler >= version 11 is used, then the agent will use ConDy and such an error will not happen.
However, for older versions, it is necessary to exclude problematic classes (for example, android packages excluded implicitly).

[shanshin]

Issue in Coverage Agent

[shanshin]

The problem is unsolvable in Gradle, because due to inline functions, it is necessary to know the list of classes of all projects and distribute such a list to each of the projects - which violates the Gradle isolation principle.
In this case, each project will depend on all the others to correctly handle calls to inline functions.