[telemetry] Complete GDPR review and approval of existing azd telemetry

[hemarina]

Problem

We do not have a completed privacy/GDPR review for the telemetry azd emits today. Until that is done we cannot retain events beyond the current window or cook them into longer-lived tables, which blocks most of the telemetry work we want to do.

What we'll do

• Inventory the fields we emit today. cli/azd/internal/tracing/fields/fields.go already annotates fields with Classification and Purpose, so it is the starting point.
• Take the inventory through review and approval.
• Record the outcome in the repo so it is reviewable and reusable next time.

Done when

• Review is complete and approved.
• The result is written down in the repo.
• Retention and cooked-table decisions are unblocked.

Notes

#9384 covers classifying new events at PR time. This issue covers what we are already collecting.

[hemarina]

Sharing progress here. I classified all GDPR rows and would like to double check with tg-msft on some classification (conversation continues in Teams). Once checked, I'll upload the row into the portal.

[hemarina]

All rows are classified and uploaded to the portal. Currently no rows need to define under https://gdpr.datasmart.ms/?q=OwnerAlias=%27azdevteam%27%20AND%20%28%28Complete%20IS%20NULL%20OR%20Complete%3D0%29%20AND%20%28Suppressed%20IS%20NULL%20OR%20Suppressed%3D0%29%20AND%20TelemetryCatalog.ProductId%3C%3E-1%29%20AND%20%28Retired%20IS%20NULL%20OR%20Retired%3D0%29