Make progress reports in event log clickable to navigate to config tree item

[Copilot]

Progress messages for long-running operators (connect, impedance_matrix, polygon operations, etc.) were not clickable in the event log, making it hard to identify which config item was being processed.

The event log UI already parses [[path]] markers as clickable links via DmsEventLog.cpp. This change prepends resultHolder.GetBackRefStr() (which produces the [[path]] format) to all operator progress reports.

Changes

• Dijkstra.cpp — impedance_matrix per-iteration and summary reports
• Connect.cpp — ConnectPointOperator (via virtual function param), ConnectInfoOperator, FastConnectOperator (direct resultHolder access)
• BoostPolygon.cpp — UnionPolygon, ProcessNumOper (inflate/deflate/filter), PolygonConnectivityOperator, polygon overlay
• BoostGeometry.cpp — all buffer operation overrides (via virtual function param)
• GridDist.cpp — GridDist iteration progress
• OperPolygon.cpp — point_in_all_polygons progress

Pattern

Where resultHolder is in scope, the prefix is computed directly. Where it isn't (virtual Calculate methods), CharPtr itemRef = "" is threaded through the call chain.

auto itemRef = resultHolder.HasBackRef() ? resultHolder.GetBackRefStr() + " " : SharedStr();

reportF(SeverityTypeID::ST_MajorTrace, "%simpedance_matrix %s %s of %s sources: resulted in %s od-pairs"
    , itemRef.c_str(), actionMsg, ...);

When no back-reference exists, itemRef is empty and the message format is unchanged.