fix: update stale cache-key fixture in BenchmarkCompileMCPWorkflow

[Copilot]

BenchmarkCompileMCPWorkflow was failing because its test fixture used github.run_id directly in a cache-memory key — now rejected by the compiler's cache-key validation, which disallows run_id in user-supplied keys since the compiler appends it automatically.

Change

Updated the fixture's cache key in compiler_performance_benchmark_test.go:

# Before (rejected — run_id in user key prevents cross-run cache restoration)
cache-memory:
  key: pr-${{ github.run_id }}

# After
cache-memory:
  key: pr-${{ env.GH_AW_WORKFLOW_ID_SANITIZED }}

• Fixes [performance] Daily benchmark: BenchmarkCompileMCPWorkflow fails due to stale cache-key fixture #48676

[Copilot]

Pull request overview

Updates the stale benchmark fixture to comply with cache-key validation and restore BenchmarkCompileMCPWorkflow, fixing #48676.

Changes:

• Replaces the prohibited github.run_id expression with the stable sanitized workflow ID.

Show a summary per file

File	Description
pkg/workflow/compiler_performance_benchmark_test.go	Updates the MCP benchmark cache key fixture.

Review details

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 1/1 changed files
• Comments generated: 0
• Review effort level: Medium