Updates the telemetry activities in the StoragePickersTelemetry class to use critical data activity classes

[DinahK-2SO]

This pull request updates the telemetry activity classes in the StoragePickersTelemetry class to use critical data activity classes instead of measures activity classes.

Telemetry updates:

• Changed BEGIN_COMPLIANT_MEASURES_ACTIVITY_CLASS to BEGIN_COMPLIANT_CRITICAL_DATA_ACTIVITY_CLASS for the FileOpenPickerPickSingleFile activity.
• Changed BEGIN_COMPLIANT_MEASURES_ACTIVITY_CLASS to BEGIN_COMPLIANT_CRITICAL_DATA_ACTIVITY_CLASS for the FileOpenPickerPickMultipleFile activity.
• Changed BEGIN_COMPLIANT_MEASURES_ACTIVITY_CLASS to BEGIN_COMPLIANT_CRITICAL_DATA_ACTIVITY_CLASS for the FileSavePickerPickSingleFile activity.
• Changed BEGIN_COMPLIANT_MEASURES_ACTIVITY_CLASS to BEGIN_COMPLIANT_CRITICAL_DATA_ACTIVITY_CLASS for the FolderPickerPickSingleFolder activity.

[DinahK-2SO]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[yeelam-gordon]

Thanks Dinah and Agne for the information.

[AgneLukoseviciute]

Looks good! Did you confirm it's showing up correctly in TRTT?

[DinahK-2SO]

Looks good! Did you confirm it's showing up correctly in TRTT?

Thanks for reminding @AgneLukoseviciute ! I tried to capture the local telemetries on TRTT, but found the StoragePickersTelemetry is still logged as "Measures", and I cannot catch them in TRTT until enabling the Test Mode + Force Opt-In

👀Did I miss something?

I am testing this this new package built by our pipeline:
Microsoft.WindowsAppSDK.Foundation.1.8.250616001-experimental.nupkg

[DinahK-2SO]

Looks good! Did you confirm it's showing up correctly in TRTT?

Thanks for reminding @AgneLukoseviciute ! I tried to capture the local telemetries on TRTT, but found the StoragePickersTelemetry is still logged as "Measures", and I cannot catch them in TRTT until enabling the Test Mode + Force Opt-In

👀Did I miss something?

Oh, I found the packaged built by nightly pipeline successfully shows the telemetry as "Critical", could be some issues with the previous pipeline run.

Thanks @AgneLukoseviciute , the telemetries are displayed as Critical. We're good to go now.