Publish profile registry to prod CDN

## Task

Publish the profile registry files to the **prod CDN** (`cdn.functions.azure.com`).

### Context

The profile registry is currently only available on **staging CDN**:
- `https://cdn-staging.functions.azure.com/public/cli/v5/profiles/v1/registry.json`
- `https://cdn-staging.functions.azure.com/public/cli/v5/profiles/v1/registry.json.sha256`

The CLI defaults to prod CDN (`cdn.functions.azure.com/public/`) — see PR #5434. Until this task is done, remote profile fetch will fail gracefully and fall back to the bundled `BuiltInProfileSource`.

### Steps

1. Run the upload pipeline targeting the **prod** storage account (use `$(prod-storage-account-name)` / `$(prod-storage-access-key)` variable groups)
2. Verify files are accessible:
- `https://cdn.functions.azure.com/public/cli/v5/profiles/v1/registry.json`
- `https://cdn.functions.azure.com/public/cli/v5/profiles/v1/registry.json.sha256`
3. Validate CDN caching headers (Cache-Control, ETag) are configured correctly per design doc (#5329)

### Acceptance Criteria

- [ ] `registry.json` and `.sha256` are live on prod CDN
- [ ] `func profile list` fetches from prod CDN without needing the env var override

Start by locating the upload pipeline referenced in the task and review PR #5434 for the prod CDN path and profile-fetch behavior. Use the prod storage variable groups, then verify both registry URLs, their Cache-Control and ETag headers against design doc #5329, and confirm `func profile list` works without the environment-variable override.

Written by the indexing model from the issue text.