Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

docs: correct autoscaling page details against the shipped manifests

Three statements on the page did not match the manifests it links to.

The intro described the HPA as scaling between minReplicas 2 and
maxReplicas 5. That is right for the vLLM and SGLang examples but not for
the nginx one, which allows up to 8, so the bounds are now described
without hardcoding one example's numbers.

The resource-requests section claimed every container sets both requests
and limits. SGLang sets a CPU request against a GPU limit and no memory
on either side, and vLLM sets memory only as a limit. What actually
matters for the HPA is that each container requests the metric its HPA
targets, which is what the text now says.

Cleanup deleted only lws-hpa. A reader who followed "Scaling on other
metrics" was told to delete that one first, so they are left with
lws-memory-hpa or lws-multi-metric-hpa still running and still scaling
the LeaderWorkerSet. It now deletes all three.

Signed-off-by: Alice C <83873276+aliceco01@users.noreply.github.com>