now the generated code actually works. as for the TODO regarding how to generate code, how about something similar as we hacked together here (without the regex, but the full power of the compiler):

• setup a generated sources folder from inside the Kotest gradle plugin once and use some semi-randomly-generated name for it
• on every test run:
  1. delete all code inside
  2. use KotlinPoet to generate the code inside that generated soruces folder. This way, no mess with escaping as in this PR, etc.
  3. run tests
  4. don't delete the generated source as they are viable for debugging and step 1 takes care of this anyway

another discovery: we run into conflicting overloads due to the generated code. seems that the new compiler plugin may have been intentionally not shipped and referenced, as it is not yet ready

* setup a generated sources folder from inside the Kotest gradle plugin once and use some semi-randomly-generated name for it

* on every test run:
  1. delete all code inside
  2. use KotlinPoet to generate the code inside that generated soruces folder. This way, no mess with escaping as in this PR, etc.
  3. run tests
  4. _don't_ delete the generated source as they are viable for debugging and step 1 takes care of this anyway

The more I think about it, the more i feel that steps 1 + 2 should be done from a dedicated gradle task that that should be specified as a dependency of all test compile tasks