Using @Property on Junit5 @Test isn't localized

Nobody has claimed this yet.

### Expected Behavior

When test is annotated with @Property, property value should be localized to specific test instance.

### Actual Behaviour

Tests in a suite executed after test with @Property annotation will keep using value from last @Property annotated test executed instead of reverting to default . Makes test results dependent on execution order.

### Steps To Reproduce

```kotlin
@Refreshable
class Foo(
@Property(name = "foo", defaultValue = "a") val value: String,
)

@MicronautTest
@TestMethodOrder(MethodOrderer.MethodName::class)
class PropertyScopedToTest(
private val foo: Foo,
) {

@Test
fun `1 - should be defaultValue`() {
assertEquals("a", foo.value)
}

@Test
@Property(name = "foo", value = "b")
fun `2 - override by annotation to b`() {
assertEquals("b", foo.value)
}

@Test
fun `3 - shouldn't this be defaultValue too`() {
assertEquals("a", foo.value)
}
}
```

### Environment Information

_No response_

### Example Application

_No response_

### Version

3.3.0

Start with the PropertyScopedToTest reproducer and its ordered JUnit 5 test methods, then trace how @Property is applied around each test instance. Confirm the lifecycle behavior that leaves "foo" set to "b" after the second test. Done means the third test observes the default value "a" without depending on execution order.

Written by the indexing model from the issue text.