Remove redundant resetObserverCounts() call in property tests

Simplified property observer test by removing unnecessary reset call.
The test now syncs the observed property once, resets counters once,
then runs assertions - eliminating redundant operations.

Author: kateinoigakukun

Tests/prelude.mjs

@@ -236,16 +236,9 @@ function BridgeJSRuntimeTests_runJsWorks(instance, exports) {
     assert.equal(ph.computedReadonly, 1554); // intValue * 2 = 777 * 2
 
     // Test property with observers
-    // First, reset observer counts to start fresh
-    exports.resetObserverCounts();
-    let initialStats = exports.getObserverStats();
-    assert.equal(initialStats, "willSet:0,didSet:0,willSetOld:0,willSetNew:0,didSetOld:0,didSetNew:0");
-    
-    // Update observedProperty to match current intValue since constructor set it to old value
+    // Sync observedProperty to match current intValue, then reset counters for clean test
     ph.observedProperty = 777; // Sync with current intValue after computed property changed it
-    
-    // Reset counters again after syncing
-    exports.resetObserverCounts();
+    exports.resetObserverCounts(); // Reset counters to start fresh test
 
     // Set property from JavaScript and verify observers are called
     ph.observedProperty = 100;