feat(uv): sample wheel build memory usage when resource_set is set

[xangcastle]

Adds a memory-monitoring layer to sdist wheel builds. When a resource_set other than "default" is declared, the wheel build action now runs under a sampler that tracks aggregate resident-set size (RSS) of the build process and all its descendants, and reports the peak to stderr.

This gives users concrete data to calibrate their resource_set estimates. Rather than guessing whether "mem_2g" is enough, they can observe what the build actually consumes.

---

Changes are visible to end-users: yes

• Searched for relevant documentation and updated as needed: yes

Test plan

• New test cases added

[aspect-workflows]

✨ Aspect Workflows Tasks

📅 Tue Jun 23 05:31:20 UTC 2026

✅ 7 successful tasks

• ✅ buildifier · ⏱ 32.8s · 🐙 GitHub Actions · ☑️ Check
  💬 Format complete (clean)
• ✅ gazelle · ⏱ 19.1s · 🐙 GitHub Actions · ☑️ Check
  💬 Gazelle complete (clean)
• ✅ test (test-e2e-bazel-8) · ⏱ 2m 17s · 🐙 GitHub Actions · ☑️ Check
  💬 Bazel test complete (153/153 passed)
• ✅ test (test-e2e-bazel-9) · ⏱ 2m 36s · 🐙 GitHub Actions · ☑️ Check
  💬 Bazel test complete (148/148 passed)
• ✅ test (test-examples-uv_pip_compile-bazel-8) · ⏱ 23.4s · 🐙 GitHub Actions · ☑️ Check
  💬 Bazel test complete (1/1 passed · 1 cached)
• ✅ test (test-root-bazel-8) · ⏱ 1m 58s · 🐙 GitHub Actions · ☑️ Check
  💬 Bazel test complete (200/200 passed)
• ✅ test (test-root-bazel-9) · ⏱ 1m 50s · 🐙 GitHub Actions · ☑️ Check
  💬 Bazel test complete (199/199 passed)

---

_{⏱ Last updated Tue Jun 23 05:34:09 UTC 2026 · 📊 GitHub API quota 105/15,000 (1% used, resets in 30m)
🚀 Powered by Aspect CLI (v2026.24.11)  |  Aspect Build · X · LinkedIn · YouTube}

[tamird]

The resource_set reservation is the right scheduler API and is already
on main. The monitor is still useful for post-OOM tuning, but its trigger
and process ownership should be narrower:

• resource_set should not implicitly enable monitoring. Reservation and
  diagnostics are independent; use an explicit monitor_memory opt-in.
• Do not use start_new_session or kill the backend process group. Bazel owns
  the action process group and its cancellation semantics. Launch the backend
  normally and sample its descendants on a best-effort basis.

The output should remain explicitly approximate Linux procfs RSS, not a hard
limit or a remote-executor sizing mechanism.

[tamird]

Superseded by #1174. The replacement is rebuilt on current main, makes
monitoring an explicit opt-in independent from resource_set, and leaves
process-group cancellation to Bazel.