Follow-up: split provision telemetry by infra.provider in downstream cooked tables

[hemarina]

Follow-up to #9090 / #9091.

Once #9091 ships (emitting the infra.provider attribute on provision / up / down), the downstream
telemetry consumers — the azd product-telemetry Kusto cooked tables and dashboards in
https://github.com/coreai-microsoft/azure-dev-tools — should be updated to surface an infra.provider
(Bicep vs Terraform) split for provisioning.

Background

infra.provider was previously only emitted on infra generate / synth, so the provision-side cooked
tables couldn't distinguish Bicep from Terraform. #9091 adds the attribute on the provision / up /
down command spans, which makes a provider split possible from command telemetry going forward.

Scope (once the field is released and adoption is visible)

• Add the infra.provider split to the provision-side command cooked tables (provisions-by-template
  and provision errors).
• Forward-only: rows predating the release won't carry the value, similar to other additive columns.

Out of scope

• deploy — not covered by feat(telemetry): emit infra.provider on provision, up, and down #9091 (deploy does not resolve an IaC provider).
• ARM-request-derived tables — the provider can't be inferred from the ARM request userAgent
  (Terraform's ARM calls don't carry the azdev/ tag), so they can't be split this way.

Prerequisites

• feat(telemetry): emit infra.provider on provision, up, and down #9091 merged and shipped in an azd release.
• Confirm cmd.provision telemetry actually carries infra.provider before wiring up the split.