test(e2e): raise pytest timeout + bump multi-user chat wait to 180s

The CI run on feat/canary-report surfaced that 90s was still not
enough for test_mcp_same_server_multi_user_via_browser on
ubuntu-latest — it timed out at the inner Playwright
wait_for_function deadline with "Timeout 90000ms exceeded" after
118s of total test time.

The test opens two browser contexts + two SSE streams and drives a
full chat turn per user in sequence. Under 2-vCPU contention the
compound pipeline genuinely takes over 90s.

- tests/e2e/pyproject.toml: timeout 120 -> 240 (pytest-level cap)
- test_v2_auth_oauth_matrix.py: send_chat_and_wait_for_terminal_message
  call sites 90000 -> 180000 (two owner/member turns, each budgeted
  for one runner-slow turn)

180s < 240s, so the inner deadline fires first with the useful
Playwright traceback instead of the generic pytest SIGTERM.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

tests/e2e/pyproject.toml

@@ -24,4 +24,4 @@ telegram = [
 asyncio_mode = "auto"
 asyncio_default_fixture_loop_scope = "session"
 asyncio_default_test_loop_scope = "session"
-timeout = 120
+timeout = 240

tests/e2e/scenarios/test_v2_auth_oauth_matrix.py

@@ -1454,12 +1454,12 @@ async def test_mcp_same_server_multi_user_via_browser(browser, auth_matrix_serve
         owner_result = await send_chat_and_wait_for_terminal_message(
             owner_page,
             "check mock mcp search",
-            timeout=90000,
+            timeout=180000,
         )
         member_result = await send_chat_and_wait_for_terminal_message(
             member_page,
             "check mock mcp search",
-            timeout=90000,
+            timeout=180000,
         )
         assert owner_result["role"] == "assistant", owner_result
         assert member_result["role"] == "assistant", member_result