Fix double event firing in DB Switch with Angular signals

Co-authored-by: mfranzke <787658+mfranzke@users.noreply.github.com>

Author: Copilot

output/react/blob-report/report-d73910a.zip

@@ -6,7 +6,16 @@ export const handleFrameworkEventAngular = (
 ): void => {
 	// Change event to work with reactive and template driven forms
 	component.propagateChange(event.target[modelValue]);
-	component.writeValue(event.target[modelValue]);
+	
+	// Skip writeValue for user-initiated change events on signal-based properties
+	// to prevent double event firing. The propagateChange call above is sufficient
+	// for notifying Angular forms of the change.
+	// For signal-based properties like 'checked', the component's signal will be
+	// updated through the normal Angular change detection cycle.
+	const isSignalBasedProperty = modelValue === 'checked' || modelValue === 'disabled';
+	if (!isSignalBasedProperty) {
+		component.writeValue(event.target[modelValue]);
+	}
 };
 
 export const handleFrameworkEventVue = (