(pipelines): Add build performance observability pipeline

[scottn12]

Description

This PR updates the placeholder pipeline added in #26299. The new pipeline does the following:

• Collects build metrics from ADO REST APIs for PR and internal builds
• Generates an HTML dashboard deployed to an Azure Static Web App (ASWA) which includes:
  • Summary metrics (total builds, avg duration, trend analysis)
  • Duration trend charts over time
  • Stage and task duration breakdown charts
  • Tables of recent and longest builds, including links to the source commits/PRs
• Will run on a daily schedule

Note: The pipeline must run in the public and internal projects to fetch PR build data and internal build data, respectively.

Next Steps/Other Considerations

• In the pipeline, there are large blocks of embedded HTML/JS/Bash code. We may want to consider factoring those into separate files.
• Create an aka.ms shortlink for the ASWA
• Seek feedback from the team on what other metrics could be useful
• Add automatic alerting if the build duration falls below a certain threshold (AB#55454)
• It seems ADO only retains a limited number of PR builds. If possible, we should try to increase the limit.
• Make ASWA only accessible internally
• Consider adding an external data store (especially if we cannot increase the public build limit).
• Add information dedicated to pnpm build locally (separate page).

Example Screenshot (Outdated)

Misc

AB#55451

[Copilot]

Pull request overview

This PR transforms a placeholder build performance observability pipeline into a functional monitoring solution. The pipeline collects build metrics from Azure DevOps REST APIs for both PR and internal builds, processes the data to generate comprehensive performance metrics, and deploys an interactive HTML dashboard to an Azure Static Web App.

Changes:

• Added daily cron schedules (2 AM UTC for PR builds, 3 AM UTC for internal builds) with logic to ensure each schedule runs in the correct project
• Implemented data collection via ADO REST APIs with parallel timeline fetching for performance
• Created metrics processing using jq to generate aggregated statistics, duration trends, and stage/task breakdowns
• Built an interactive dashboard with Chart.js visualizations, sortable tables, and tabbed navigation for PR vs internal builds

[anthony-murphy]

have you done a security review of the plan here. just want to ensure we are accuring any additional security debt by adding this all.

[scottn12]

I was working with @Abe27342 for security questions/concerns up until this point. Is there a formal security review this should go through?

[anthony-murphy]

Did you evaluate whether this repo or the internal ADO repo is a better fit for this to live in?

[scottn12]

Did you evaluate whether this repo or the internal ADO repo is a better fit for this to live in?

@anthony-murphy yes, that was my original plan/preference. Unfortunately, internal ADO projects cannot access data from public ADO projects (security setting), so we would be unable to fetch PR data. I was also looking into an alternative using telemetry (instead of ADO REST APIs), but that added even more complexity/security issues.