Needs debugging and testing
* load kex-runner jar from github (build.gradle.kts toplevel)
* setup code for kex properties
* KexErrorManager based on LLMErrorManager
* KexProcessManager based on EvoSuiteProcessManager
* Basic UI element (button for running kex)
* kex works only for the class codeType (todo funciton and line if possible)
* read resource files kex.policy and modules.info

use a provided kex path for now instead of downloading jar and adding dependency
use ProcessBuilder (jdk) instead of OSProcessHandler (IJ sdk)
use kex.py instead of building java command directly
generate Report objects by reading generated java classes

Deleted stuff:
running Kex through through OSProcessHandler (IJ sdk)
running Kex with kex.py
downloading kex from github in build.gradle.kts

…therInfo

…updates

arguably overkill solution of modify PsiMethodWrapper class
added parameter names, types and return tyepes explicitly
updated implementation for java and kotlin

…' into edwin1729/improvement/kex-integration

For multimodule projects using TestSpark the correct module's
build directory path is passed based on the location of code for which
tests are generated

also fixed a bug with the way options were passed to kex subprocess
made them a list of strings instead of a single big space separated string

This also includes a simple string based mapping to jvm types through type erasure

It no longer depends on the order of the methods generated

This is expected by TestSpark. Relevant file TestProcess.kt:createXmlFromJacoco:109

…ding