…eduplication

This commit addresses CI failures from GitHub Actions runs:
- Fixed 5 clippy uninlined_format_args warnings in Rust code
- Added 140+ comprehensive unit tests for new Vue components

Backend fixes:
- correlation.rs: Inline format string variables (2 fixes)
- deduplication.rs: Inline format string variables (2 fixes)
- correlation.rs (service): Inline format string variable (1 fix)

Frontend tests added (71.96% coverage, up from 71.54%):
- TagInput.spec.ts: 19 tests for tag input component
- SemanticGroupItem.spec.ts: 19 tests for semantic group editing
- IncidentList.spec.ts: 30 tests for incident list display
- DeduplicationConfig.spec.ts: 8 tests for dedup configuration
- OrganizationDeduplicationSettings.spec.ts: 8 tests for org settings
- SemanticFieldGroupsConfig.spec.ts: 61 tests for field group management

The new tests provide solid coverage of core functionality including:
- Component rendering and structure
- User interactions (clicks, inputs, form submissions)
- Data validation and formatting
- State management and prop updates
- Preset loading and configuration
- Edge cases and error handling

Prevents TypeError when viewing SQL-based alerts where conditions field is null instead of an object with length property.

Separates deduplication configuration into two distinct levels:
- Organization-level: Semantic field groups + default time window (global)
- Per-alert level: Fingerprint fields + time window override (per-alert)

Backend Changes:
- Add OrganizationDeduplicationConfig for org-wide semantic groups
- Keep DeduplicationConfig (from main) for per-alert fingerprint fields
- Update API handlers to use OrganizationDeduplicationConfig
- Update service layer for proper type separation
- All type references updated across codebase

Frontend Changes:
- OrganizationDeduplicationSettings.vue: Remove fingerprint fields UI
- SemanticFieldGroupsConfig.vue: Add showFingerprintFields prop
- DeduplicationConfig.vue: Unchanged (per-alert, matches main branch)
- Updated descriptions to clarify config separation

Testing:
- Add test_dedup_correlation.sh for API integration testing
- Add TESTING_DEDUP_CORRELATION.md comprehensive test guide
- Cargo check passes ✅

How it works:
1. Org-level defines semantic groups: {"host": ["host", "hostname", "node"]}
2. Per-alert specifies actual fields: ["hostname", "service_name"]
3. Enterprise module uses semantic groups for reverse lookup/mapping

Implements cross-alert deduplication that suppresses alerts from different
alert rules when they share semantic dimensions with recently fired alerts.

Key Changes:
- Add cross_alert_dedup flag to OrganizationDeduplicationConfig
- Add semantic dimension extraction helpers to org config
- Update deduplication service to fetch and pass org config to enterprise
- Add find_matching_semantic_fingerprints() for cross-alert lookups

Behavior:
- cross_alert_dedup=false (default): Per-alert dedup only (backward compatible)
  * Alert A: fingerprint="alert_A:srv01:api"
  * Alert B: fingerprint="alert_B:srv01:region" → Both sent

- cross_alert_dedup=true (new): Cross-alert semantic dedup
  * Alert A fires: semantic_dims={host:srv01, service:api}
  * Alert B fires 30s later: semantic_dims={host:srv01, region:us-east}
  * Result: Alert B suppressed (shares host=srv01 dimension)

Enterprise Module Requirements:
- Updated calculate_fingerprint() signature with org_config parameter
- Semantic fingerprint format: "dim1=val1,dim2=val2" (no alert ID)
- fingerprint_matches_dimensions() for overlap detection
- See CROSS_ALERT_DEDUP_SPEC.md for full specification

Benefits:
- Prevents alert storms from related issues across different monitors
- Semantic grouping allows flexible field name variations
- Opt-in feature with backward compatibility

Fixes correlation service to fetch semantic groups from org-level
deduplication config instead of per-alert config.

Changes:
- Update scheduler/handlers.rs to fetch semantic groups from org config
- Remove duplicate claim_parser_function block (compilation error)
- Semantic groups now correctly sourced from OrganizationDeduplicationConfig

Behavior:
- Correlation uses org-wide semantic field groups
- Consistent with deduplication's use of org-level groups
- Per-alert config no longer has semantic_field_groups field