<!-- 
If this PR updates documentation, please update all relevant versions of
the docs, see:
https://github.com/kotest/kotest/tree/master/documentation/versioned_docs
The documentation at
https://github.com/kotest/kotest/tree/master/documentation/docs is the
documentation for the next minor or major version _TO BE RELEASED_
-->
**Overview**

This PR resolves an issue that occurs when using the `Koin` dependency
injection framework in a Property-Based Testing environment. This is
based on the discussion in GitHub issue kotest#2171.

**The Problem**

When using property-based testing functions like Kotest's `checkAll`
with `KoinListener`, the Koin context is shared across all iterations of
the test. This is because `KoinListener` only starts and stops the Koin
context at the `TestCase` level, and all iterations within a `checkAll`
block are considered part of a single `TestCase`.

As a result, an object declared in a Koin module during the first
iteration (e.g., `declareMock { Repository(arg) }`) is reused in
subsequent iterations. For example, `get<Service>()` would always
receive `Repository(true)` in the second run. This violates the
fundamental principle of test isolation, where each test run should be
independent, thereby undermining the reliability of property-based
tests.

**The Solution**

To address this, this PR introduces `KoinPropTestListener`, a new
listener that implements the `PropTestListener` interface.

The `KoinPropTestListener` ensures proper test isolation by starting the
Koin context with `startKoin` immediately before **each iteration** of a
property test begins, and shutting it down with `stopKoin` immediately
after the iteration completes.

**Before:**

With `KoinListener`, isolation between property test iterations was not
guaranteed.

```kotlin
// Using KoinListener with property-based tests...
checkAll<Boolean> { arg -> // true, false
  declareMock { Repository(arg) }
  get<Service>() // The second iteration would still get Repository(true)
}
```

**After:**

`KoinPropTestListener` creates a fresh Koin context for each iteration,
ensuring complete test isolation.

```kotlin
checkAll<Boolean>(
    PropTestConfig(listeners = listOf(KoinPropTestListener(myModule)))
) { a ->
    val currentService: MyService = get { parametersOf(a) }
    currentService.a shouldBe a // A new Service instance is injected every time
}
```

This change allows developers to reliably use `Koin` with property-based
tests, ensuring that dependencies for each test iteration are managed in
a clean and isolated manner.

**Related Issue**

*   Fixes kotest#2171

Signed-off-by: belljun3395 <195850@jnu.ac.kr>
Co-authored-by: Sam <sam@sksamuel.com>