fix: disable anyio pytest plugin

[xangcastle]

Problem

When anyio is a direct or transitive dependency of a py_test target, its pytest plugin auto-registers via the pytest11 entry point. This causes interference with test collection and execution in environments that don't explicitly configure anyio's async backend.

Fix

Add and e2e sample with -p no:anyio to the pytest args.

---

Changes are visible to end-users: no

Test plan

• New test cases added

[aspect-workflows]

✨ Aspect Workflows Tasks

📅 Wed Jun 10 22:57:55 UTC 2026

✅ 7 successful tasks

• ✅ buildifier · ⏱ 24.3s · 🐙 GitHub Actions · ☑️ Check
  💬 Format complete (clean)
• ✅ gazelle · ⏱ 18.1s · 🐙 GitHub Actions · ☑️ Check
  💬 Gazelle complete (clean)
• ✅ test (test-e2e-bazel-8) · ⏱ 34m 8s · 🐙 GitHub Actions · ☑️ Check
  💬 Bazel test complete (62/62 passed)
• ✅ test (test-e2e-bazel-9) · ⏱ 36m 26s · 🐙 GitHub Actions · ☑️ Check
  💬 Bazel test complete (62/62 passed)
• ✅ test (test-examples-uv_pip_compile-bazel-8) · ⏱ 17.7s · 🐙 GitHub Actions · ☑️ Check
  💬 Bazel test complete (1/1 passed · 1 cached)
• ✅ test (test-root-bazel-8) · ⏱ 38m 5s · 🐙 GitHub Actions · ☑️ Check
  💬 Bazel test complete (123/123 passed)
• ✅ test (test-root-bazel-9) · ⏱ 36m · 🐙 GitHub Actions · ☑️ Check
  💬 Bazel test complete (122/122 passed)

---

_{⏱ Last updated Wed Jun 10 23:36:10 UTC 2026 · 📊 GitHub API quota 252/15,000 (2% used, resets in 6m, throttle 3×)
🚀 Powered by Aspect CLI (v2026.22.44)  |  Aspect Build · X · LinkedIn · YouTube}

[jbedard]

Now this is just an example in e2e? Is that worth merging into 1.x?