Add automatic instrumentation filter to project classes

[shanshin]

Due to the incompatibility of some libraries with Kover instrumentation, errors may occur in the instrumentation of classes that are not related to the project.
There is a need to filter out all classes that are not related to projects.

This can be implemented by performing the tasks of compiling all dependencies strictly before running the tests, finding packages that relate to the application, and transferring these packages to the CommandLineArgumentProvider.

This solution has the following disadvantages:

• Kover implicitly add dependencies to the build between compilation Gradle tasks and test tasks
• If the compilation task depends on the testing task of another project, and project is specified as a Kover dependency, then a cyclic dependency between tasks appears

[shanshin]

This task will be taken into account when migrating to Kotlin Gradle Plugin.

In the future, it will be moved to the Kotlin task tracker, or closed if it loses relevance.