[Docs] Follow the backend example's tuning tests, and state the backends page without implementation-specific counts

[lcy-seso]

Problems

• Follow TileOPs main: serving_target, built_entries, and a kernel's request_tune and config lcy-seso/tileops-backend-example#4 added tests/test_tuning.py; the backends page lists four test files and 24 passed.
• The page states facts that go stale with the next change: the test count, the GPU it ran on, the dev image's tilelang tag, the number of test files, how many kernels GEMM declares, and the list of CUDA architecture markers.
• The template step said only the op and target names need substituting; the tests also import the package and the kernel classes, create tensors on CPU and assert the CPU device type.
• The link to the example's tests/ points at tree/main, which returns 404: the repository's branch is master.

Changes

• The layout table lists tests/test_tuning.py, English and Chinese.
• The test run says all tests pass, none skipped, with and without a GPU; the docker command takes a published <tag>, in the form the development guide's dev-image section gives.
• The template step lists the three changes the tests need: the package, target, op and kernel class names; the device; and op- or kernel-specific assertions. It links tree/master/tests. GEMM "declares several" kernels.
• The marker table names architecture markers by their form, sm<NN>, and counts three kinds of marker.
• The Chinese page is reworded as technical prose; the template steps are statements.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.