This PR adds the frameworkName field to critical Windows ML telemetry
events to ensure proper event attribution and prevent data loss.

The frameworkName field is added to ensure that Windows ML events are
not lost and do not require joins with events that might have been
emitted outside the scope of the time span the processing scripts check
for long-running apps/processes. This allows each event to be
self-contained with framework identification.

The following telemetry events now include the frameworkName field:

1. **SessionCreationStart** - Logs when session creation begins
2. **SessionCreation** - Logs session creation details including model
metadata
3. **RuntimeError** - Logs runtime errors (both DEBUG and release
builds)
4. **RuntimePerf** - Logs runtime performance metrics including total
runs and duration
5. **AutoEpSelection** - Logs automatic execution provider selection
policy and results
6. **ProviderOptions** - Logs execution provider configuration options

All events now include TraceLoggingString(ORT_CALLER_FRAMEWORK,
"frameworkName") to maintain consistent framework identification across
the telemetry pipeline.

---------

Co-authored-by: Angela Serrano Brummett <[email protected]>

This cherry-picks the following commits for the 1.24.2 release:
- #27096
- #27077
- #26677
- #27238
- #27213
- #27256
- #27278
- #27275
- #27276
- #27216
- #27271
- #27299
- #27294
- #27266
- #27176
- #27126
- #27252

---------

Co-authored-by: Xiaofei Han <[email protected]>
Co-authored-by: Jiajia Qin <[email protected]>
Co-authored-by: Yulong Wang <[email protected]>
Co-authored-by: qti-monumeen <[email protected]>
Co-authored-by: Ankit Maheshkar <[email protected]>
Co-authored-by: Eric Crawford <[email protected]>
Co-authored-by: Copilot <[email protected]>
Co-authored-by: guschmue <[email protected]>
Co-authored-by: Guenther Schmuelling <[email protected]>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: angelser <[email protected]>
Co-authored-by: Angela Serrano Brummett <[email protected]>
Co-authored-by: Misha Chornyi <[email protected]>
Co-authored-by: hariharans29 <[email protected]>
Co-authored-by: eserscor <[email protected]>
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Baiju Meswani <[email protected]>
Co-authored-by: Adrian Lizarraga <[email protected]>
Co-authored-by: Ti-Tai Wang <[email protected]>
Co-authored-by: bmehta001 <[email protected]>

This PR adds the frameworkName field to critical Windows ML telemetry
events to ensure proper event attribution and prevent data loss.

The frameworkName field is added to ensure that Windows ML events are
not lost and do not require joins with events that might have been
emitted outside the scope of the time span the processing scripts check
for long-running apps/processes. This allows each event to be
self-contained with framework identification.

The following telemetry events now include the frameworkName field:

1. **SessionCreationStart** - Logs when session creation begins
2. **SessionCreation** - Logs session creation details including model
metadata
3. **RuntimeError** - Logs runtime errors (both DEBUG and release
builds)
4. **RuntimePerf** - Logs runtime performance metrics including total
runs and duration
5. **AutoEpSelection** - Logs automatic execution provider selection
policy and results
6. **ProviderOptions** - Logs execution provider configuration options

All events now include TraceLoggingString(ORT_CALLER_FRAMEWORK,
"frameworkName") to maintain consistent framework identification across
the telemetry pipeline.

---------

Co-authored-by: Angela Serrano Brummett <[email protected]>

This PR adds the frameworkName field to critical Windows ML telemetry
events to ensure proper event attribution and prevent data loss.

## Reason
The frameworkName field is added to ensure that Windows ML events are
not lost and do not require joins with events that might have been
emitted outside the scope of the time span the processing scripts check
for long-running apps/processes. This allows each event to be
self-contained with framework identification.

## Events Modified
The following telemetry events now include the frameworkName field:

1. **SessionCreationStart** - Logs when session creation begins
2. **SessionCreation** - Logs session creation details including model
metadata
3. **RuntimeError** - Logs runtime errors (both DEBUG and release
builds)
4. **RuntimePerf** - Logs runtime performance metrics including total
runs and duration
5. **AutoEpSelection** - Logs automatic execution provider selection
policy and results
6. **ProviderOptions** - Logs execution provider configuration options

All events now include TraceLoggingString(ORT_CALLER_FRAMEWORK,
"frameworkName") to maintain consistent framework identification across
the telemetry pipeline.

---------

Co-authored-by: Angela Serrano Brummett <[email protected]>

This cherry-picks the following commits for the release:
- #27252 Record service in telemetry events
- #27256 Log Framework name to more Windows ML relevant events

---------

Co-authored-by: bmehta001 <[email protected]>
Co-authored-by: angelser <[email protected]>
Co-authored-by: Angela Serrano Brummett <[email protected]>
Co-authored-by: Aditya Rastogi <[email protected]>