test(envlite): use truly invalid cached port in phase1 test

The fixture used 9999, which falls inside the 1..65535 range that
envlite_phase1_discover_port treats as a valid cached port — so the
function returned 9999 and the assertion that the port came from the
8100..8899 auto-discovery pool would have failed if the suite ever
got that far. Use 70000 so the cache-out-of-range path is actually
exercised.

Author: sirreal

tools/local-env/tests/test_phase1.php

@@ -45,7 +45,9 @@ function test_phase1_uses_cached_port_when_in_range() {
 function test_phase1_ignores_cache_when_out_of_range() {
     $dir = envlite_test_tmpdir('phase1-bad-cache');
     mkdir($dir . '/.envlite');
-    file_put_contents($dir . '/.envlite/port', "9999\n");
+    // 70000 is outside the 1..65535 cached-port acceptance window, so the
+    // cache must be ignored and a fresh port picked from the auto pool.
+    file_put_contents($dir . '/.envlite/port', "70000\n");
     $port = envlite_phase1_discover_port($dir, null);
     envlite_assert($port >= 8100 && $port <= 8899);
 }