fix: Fixing CNI Telemtry Service run by CNS

[behzad-mir]

This PR fixes an issue where the CNI telemetry service was failing to start by CNS due to an empty Application Insights (AI) instrumentation key. The telemetry service was being initialized with a basic configuration that lacked the proper AI settings from the CNS configuration.

Requirements:

• uses conventional commit messages
• includes documentation
• adds unit tests
• relevant PR labels added

Notes:

[Copilot]

Pull Request Overview

This PR fixes the CNI telemetry service initialization issue where it was failing to start due to an empty Application Insights instrumentation key. The fix ensures that the telemetry service uses the proper AI configuration from the CNS configuration instead of an empty basic configuration.

• Updates the startTelemetryService function to accept CNS configuration and properly initialize AI telemetry settings
• Adds validation to check for Application Insights instrumentation key before starting the telemetry service
• Introduces proper telemetry configuration mapping from CNS settings to AI config

[Copilot]

There's a typo in the PR title 'Telemtry' which should be 'Telemetry'. While this constant name is correct, ensure consistency in naming throughout the codebase.

[tamilmani1989]

we should check other way and remove else?

if cnsconfig.TelemetrySettings.AppInsightsInstrumentationKey == "" {
  logger.Printf("No Application Insights key provided for CNI telemetry service")
  return
}
err = tb.CreateAITelemetryHandle(aiConfig, ts.DisableTrace, ts.DisableMetric, ts.DisableEvent)

[santhoshmprabhu]

Discussed in the team meeting today - we may want to consider doing telemetry for CNI directly in CNI rather than CNS, to account for scenarios where CNI can't talk to CNS.
Tagging @tamilmani1989 as decided in the call.