fix(pwndbg): separate the words in the debugger-context limit message (#5372)

The 64 MiB reply-budget refusal rendered as "exceeds64 MiB" because the
message word and the limit were joined. The pwntools sibling names the
same budget as "exceeds the 64 MiB reply budget"; use that wording.

The output-limit path had no producer regression, so the pwndbg suite
gains one that drives the real 64 MiB boundary, and the suite is now part
of test:python instead of running only when invoked by hand.

Co-authored-by: XiaoBinGan <XiaoBinGan@users.noreply.github.com>

package.json

@@ -139,7 +139,7 @@
     "test": "npm run test:with-build",
     "test:with-build": "npm run test:prepare && vitest run",
     "test:run": "vitest run",
-    "test:python": "python3 -m unittest bridge/native/test_rea_lldb_tracer.py bridge/mitmproxy/test_capture.py -v && python3 -m unittest discover -s experiments/analysis-efficiency -p 'test_*.py' -v",
+    "test:python": "python3 -m unittest bridge/native/test_rea_lldb_tracer.py bridge/pwndbg/test_core_context.py bridge/mitmproxy/test_capture.py -v && python3 -m unittest discover -s experiments/analysis-efficiency -p 'test_*.py' -v",
     "test:local": "node scripts/run-development-tests.mjs local",
     "test:fast": "node scripts/ci/test-group.mjs source",
     "test:built": "node scripts/ci/test-group.mjs built",