Fix IED capability and fault-record window regressions

[masarray]

Root causes

Two WPF regressions were found after adding the per-IED capability actions.

1. Capability-state updates were subscribed directly to Iec61850MonitorDevice.PropertyChanged. Online discovery publishes state changes from worker threads, so the handler touched WPF buttons from a non-UI thread and aborted an otherwise successful MMS discovery.
2. FaultRecordWindow used implicit binding modes for read-only view-model properties. Run.Text attempted a source update for the getter-only EndpointText property and threw while the window was being shown.
3. The capability panel originally shared the lifecycle-action grid row and could visually cover the Stop button.

Fix

• marshal every capability refresh through the owning IED card dispatcher
• verify the card remains loaded and bound to the same IED before applying state
• place GOOSE, SMV, and File Transfer in a dedicated compact card row
• use OneTime for immutable DeviceName and EndpointText labels
• use explicit OneWay for dynamic display-only state and DataGrid columns
• reserve TwoWay only for editable directory fields and record selection
• run a binding-mode regression guard from the existing source-validation workflow

Expected result

• accepted ACSE/MMS associations proceed into online discovery
• File Transfer no longer covers the Stop action
• Fault Record Transfer opens without the read-only binding exception
• future implicit TwoWay regressions fail CI before merge

Validation

The Windows application workflow validates source boundaries, binding modes, UX invariants, ARIEC61850 API compatibility, restore, Release build, portable x64 publish, and artifact upload. Live testing against the reported IED remains the final acceptance test.

[masarray]

Superseded by #59, which re-audited and ported every still-relevant fix onto the current main branch without the stale history or merge conflicts. The replacement passed source/binding guards, UX invariants, ARIEC61850 compatibility, Release build, portable publish, and artifact upload, then merged as commit 07c2dec2d8c181a762c401161919379a17212ef6.