llm/custom_ops: follow test code conventions

[gpires-meta]

Summary:
Rename Test Suites in test_sdpa_with_kv_cache to follow internal tooling conventions and make test target static listable.

Previously, some of the Test Suites in the modified test file did not satisfy the condition:

• Test Suite's name must contain Test

This diff makes it so that the Test Suites follow the expected conventions.

Benefits

Following the conventions grants the test targets:

• Faster test listing
• Better dev experience in VSCode

Differential Revision: D85428922

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 3 New Failures, 2 Unrelated Failures

As of commit 7fed498 with merge base de56c81 ():

NEW FAILURES - The following jobs have failed:

• pull / test-samsung-models-linux / linux-job (gh)
  RuntimeError: Command docker exec -t 28decc7a27e58a876d4014f50edd91e06bd5260e0c493f4425f95af80e0f45f7 /exec failed with exit code 1
• pull / unittest-nxp-neutron / linux-job (gh)
  RuntimeError: Command docker exec -t 78cd712b588b993bcd1746ded450adf9f2c8e2c2de7bebeb4e51dc04b469daee /exec failed with exit code 1
• Test Metal Backend / export-voxtral-metal-artifact / macos-job (gh)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 2

FLAKY - The following job failed but was likely due to flakiness present on trunk:

• pull / unittest / linux / linux-job (gh) (detected as infra flaky with no log or failing log classifier)

BROKEN TRUNK - The following job failed but was present on the merge base:

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

• pull / unittest-editable / linux / linux-job (gh) (trunk failure)

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

[meta-codesync]

@gpires-meta has exported this pull request. If you are a Meta employee, you can view the originating Diff in D85428922.

[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.