docs(k8s-proxy-llm-workflow): use legacy /tr MCP tools for Routine A

`keploy cloud replay --branch-name` writes its uploaded report into
the legacy /tr collection (`testrunReports` in Mongo). The playbook
was directing the agent at the api-testing test-suite-run surface
(`listTestRuns({kind: "test_suite_run"})` + `get_session_report`),
which queries a different collection — so Phase A1 would return
nothing for the dev's branch and Phase A2 (even when given a
test_run_id) would return the sandbox-session shape (`failed_steps[]`
/ `mock_mismatch_dominant`) instead of legacy /tr (per-test-case
`oss_report.result.*` / `oss_report.mock_mismatches`). The agent's
autonomous diagnosis path would silently fall back to asking the dev.

Switch the playbook to the legacy /tr tools that match the underlying
data model:

- Phase A1: `listTestReports({appId, branch_id, status: "FAILED", limit: 5})`,
  with `source: "ci"` for the CI form.
- Phase A2: `getTestReportFull({appId, reportId})` — returns rollup +
  every test set + per-test-case diff + `mock_mismatches` in one
  round-trip; `mock_mismatches_only=true` flag for mock-drift focus.
- Phase A3 / A4 / A5: read fields as `oss_report.result.body_result[]`
  / `oss_report.mock_mismatches.{expected_mocks,actual_mocks}`; write
  via `updateTestCase` (legacy /tr's edit tool) instead of
  `update_test_suite` (api-testing's suite-edit tool).
- "Run report" URL goes from `/tr?appId=<app_id>&branch=<branch>`
  (the list page with a non-existent `branch` query param) to
  `/tr/<test_run_id>?appId=<app_id>` (the actual detail page).

Updates the hard rules, the three Phase tables in Step 3, and the
Scenario 2 / 3 narrative examples for consistency.

Signed-off-by: Charan Kamarapu <kamarapucharan@gmail.com>

Author: charankamarapu