Rename private address space overrides ports in tests

The tests still use "private" as the internal naming because the specific spec they are testing, is awaiting a decision on whether to call it "private" or "local".

fetch/private-network-access/resources/support.sub.js

@@ -76,13 +76,13 @@ async function postMessageAndAwaitReply(target, message) {
 const SERVER_PORTS = {
   "http": {
     "local": {{ports[http][0]}},
-    "private": {{ports[http-private][0]}},
+    "private": {{ports[http-local][0]}},
     "public": {{ports[http-public][0]}},
   },
   "https": {
     "local": {{ports[https][0]}},
     "other-local": {{ports[https][1]}},
-    "private": {{ports[https-private][0]}},
+    "private": {{ports[https-local][0]}},
     "public": {{ports[https-public][0]}},
   },
   "ws": {

infrastructure/assumptions/non-local-ports.sub.window.js

@@ -9,8 +9,8 @@
 // More tests can be found in `fetch/private-network-access/`.
 
 const alternatePorts = {
-  httpPrivate:  "{{ports[http-private][0]}}",
-  httpsPrivate: "{{ports[https-private][0]}}",
+  httpPrivate:  "{{ports[http-local][0]}}",
+  httpsPrivate: "{{ports[https-local][0]}}",
   httpPublic:   "{{ports[http-public][0]}}",
   httpsPublic:  "{{ports[https-public][0]}}",
 };