fix(inspur): correctly handle PCIe Assert/Deassert GPU fault events

Three related fixes for IDL event processing:

1. idl.go: include EventType in dedup key so Deassert events are no
   longer silently dropped as duplicates of their Assert counterparts.

2. gpu_status.go: treat Deassert events as clearing all GPU faults —
   previously the code re-applied the same faulty GPU set from the
   description, leaving GPUs stuck in Critical even after alarm cleared.

3. reanimator_models/converter: add bmc_event_summary section to the
   Reanimator export — a deduplicated Critical/Warning event table with
   Active/Resolved status derived from Assert/Deassert pairs.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

internal/parser/vendors/inspur/gpu_status.go

@@ -56,10 +56,12 @@ func applyGPUStatusFromEvents(hw *models.HardwareConfig, events []models.Event)
 	}
 
 	for _, e := range relevantEvents {
+		// Deassert means the alarm was cleared: all GPUs return to OK.
+		isDeassert := strings.EqualFold(strings.TrimSpace(e.EventType), "Deassert")
 		faultySet := extractFaultyGPUSet(e.Description)
 		for idx, gpu := range gpuByIndex {
 			newStatus := "OK"
-			if faultySet[idx] {
+			if !isDeassert && faultySet[idx] {
 				newStatus = "Critical"
 				lastCriticalDetails[idx] = strings.TrimSpace(e.Description)
 			}