Add PLAYER_TELEMETRY_SUPPORT guards around std::map telemetry blocks in pipeline state changes

[Copilot]

Pipeline state change handling in SetStateWithWarnings lacked telemetry instrumentation, and no mechanism existed to conditionally compile telemetry support.

Changes

• PlayerTelemetry.h — New PlayerTelemetry2 class with send(marker, iMap, sMap, fMap) accepting typed std::map payloads for int, string, and float values
• PlayerTelemetry.cpp — Default implementation logging all telemetry entries via MW_LOG_MIL
• InterfacePlayerRDK.cpp — Telemetry blocks added under #ifdef PLAYER_TELEMETRY_SUPPORT in every case of the SetStateWithWarnings switch, mapping current/pending/target state into typed maps before dispatch:

#ifdef PLAYER_TELEMETRY_SUPPORT
    {
        std::map<std::string, int> i;
        std::map<std::string, std::string> s;
        std::map<std::string, float> f;
        s["cur"]  = gst_element_state_get_name(current);
        s["pen"]  = gst_element_state_get_name(pending);
        // GstState is an enum; transmit numeric value (stable for decoding on the backend)
        i["tgt"]  = static_cast<int>(targetState);
        PlayerTelemetry2 telemetry;
        telemetry.send("MW_PIPELINE_STATE_CHANGE_FAILURE", i, s, f);
    }
#endif

Covered cases: FAILURE, SUCCESS, ASYNC, and default (→ MW_PIPELINE_STATE_CHANGE_UNKNOWN).

• CMakeLists.txt — CMAKE_PLAYER_TELEMETRY_SUPPORT option conditionally appends PlayerTelemetry.cpp and defines -DPLAYER_TELEMETRY_SUPPORT; PlayerTelemetry.h added to headers and install target

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.