[ET-VK][testing] Add per-shader timing breakdown to benchmark output

[SS-JIA]

Stack from ghstack (oldest at bottom):

• [ET-VK][qconv] Add flexible layout impl for im2col #17249
• [ET-VK][qconv] Add flexible layout impl for quantized pointwise conv #17221
• [ET-VK][testing] Create dedicated test binary for pointwise convolutions #17220
• [ET-VK][qconv] Add layout-agnostic general shader for quantized conv #17219
• [ET-VK][quantization] Add layout-flexible clone for int8x4 tensors #17171
• [ET-VK][qconv] Add layout-flexible impl of quantized depthwise conv2d #17108
• [ET-VK][ez] Implement helper functions to get fastest moving dim #17107
• [ET-VK][quantization] Implement layout-flexible quantize/dequantize operators #17106
• [ET-VK] Add alignment fields to PackedDimInfo for padded size calculation #17170
• -> [ET-VK][testing] Add per-shader timing breakdown to benchmark output #17105

Previously, benchmark results only showed aggregate GPU timing for each
test case, making it difficult to identify which specific shaders were
executing and how they contributed to the overall runtime. This change
adds per-shader timing instrumentation to enable quick identification
of performance bottlenecks.

Key changes:

• Add ShaderTiming struct to track individual shader execution times
  across iterations
• Add collect_per_shader_timing_us() helper that extracts timing data
  from the querypool on a per-shader basis (vs the previous aggregate)
• Update BenchmarkResult::print_row() to display shader names and
  their individual timings. When multiple shaders participate, each
  shader's average time is shown on its own line before the summary row
• Add string utility helpers (layout_abbrev, storage_type_abbrev,
  repr_str, shape_string) for generating concise test case names
• Adjust column widths for better terminal fit

Differential Revision: D91945038

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/17105

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❌ 2 New Failures, 1 Pending, 3 Unrelated Failures

As of commit 82e283c with merge base 1cffd23 ():

NEW FAILURES - The following jobs have failed:

• pull / unittest / linux / linux-job (gh)
  RuntimeError: Command docker exec -t 27ac77a604e32244136a3d0009d820612c9e22a941eddf075ec54121c9f7426f /exec failed with exit code 1
• pull / unittest-editable / linux / linux-job (gh)
  RuntimeError: Command docker exec -t 180c3764d072b14436ca4d3ea27c9f2375a9d1dce5f71f7588847ef157efc80b /exec failed with exit code 1

BROKEN TRUNK - The following jobs failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• pull / test-samsung-quantmodels-linux / linux-job (gh) (trunk failure)
  ##[error]The operation was canceled.
• pull / unittest / macos / macos-job (gh) (trunk failure)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 1
• pull / unittest-editable / macos / macos-job (gh) (trunk failure)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 1

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.