Add SLD impact highlights for contingencies, actions, and overloads

[marota]

Summary

This PR adds visual highlighting of impacted assets on Single Line Diagrams (SLDs) to help users quickly identify which equipment is affected by contingencies, remedial actions, and overloaded lines. Four distinct visual styles are applied: orange glow for contingency elements, yellow glow for action targets, dashed orange for overloaded lines, and purple glow for affected breakers/switches.

Key Changes

• CSS Styling (App.css and standalone_interface.html):

  • Added four new highlight classes with distinct visual styles:
    • .sld-highlight-contingency: Orange glow (#ff9800) for N-1 contingency elements
    • .sld-highlight-action: Yellow glow (#fffb00) for action target equipment
    • .sld-highlight-overloaded: Dashed orange (#ff8c00) for overloaded lines
    • .sld-highlight-breaker: Purple glow (#e040fb) for affected breakers/switches
  • Each style includes drop-shadow filters and stroke styling for SVG elements

• Frontend Logic (VisualizationPanel.tsx):

  • Added new useEffect hook to manage SLD impact highlights independently of delta flow coloring
  • Implemented equipment ID lookup with multiple fallback strategies:
    • Exact metadata lookup with dot/underscore sanitization variants
    • Substring matching against metadata equipment IDs
    • Fallback substring search against SVG element IDs
  • Highlights contingency element when viewing N-1 or action tabs
  • Highlights action targets (lines, generators, loads, PST taps) when viewing action tab
  • Highlights affected breakers/switches from action topology with fallback parsing of action descriptions
  • Highlights overloaded lines when viewing N-1 or action tabs
  • Prevents duplicate highlighting of the same cell element

• Backend Enhancement (recommender_service.py):

  • Extended action topology enrichment to include pst_tap, substations, and switches fields
  • Added logic to supplement missing switches data from the original action dictionary entry, since grid2op Action objects may not carry this attribute
  • Applied same supplementation in both _enrich_actions() and get_action_detail() methods

• Type Updates:

  • Added ActionDetail import to component type definitions
  • Updated SldOverlayProps interface to include selectedBranch, result, and selectedActionId props

Implementation Details

• The highlight logic uses vlOverlay.actionId (set when overlay opens) rather than component-level selectedActionId to ensure consistency
• Equipment ID matching handles common naming variations (dots vs underscores) to accommodate different naming conventions
• Action description parsing extracts breaker/switch names from French text patterns like "Ouverture/Fermeture" and "OC ' DJ_OC'"
• Highlights are cleared and recomputed whenever SLD metadata, tab, or action details change

https://claude.ai/code/session_01CWNLrpSw2HRn1qURUo8cYX