fix: don't escape base path in ecmascript runtime to allow for URLs (v…

…ercel/turborepo#7093)

### Description

next's asset prefix can be a full URL, I think we can assume that the
basepath itself is valid.
we probably also want to ensure that the `chunkPath` never contains
invalid URL characters at build time so we don't need to escape anything
at all at runtime.

Need to make sure it passes all next.js tests
#61090

Closes PACK-2282

crates/turbopack-ecmascript-runtime/js/src/dev/runtime/base/runtime-base.ts

@@ -1291,10 +1291,10 @@ function getOrInstantiateRuntimeModule(
  * Returns the URL relative to the origin where a chunk can be fetched from.
  */
 function getChunkRelativeUrl(chunkPath: ChunkPath): string {
-  return `${CHUNK_BASE_PATH}${chunkPath}`
+  return `${CHUNK_BASE_PATH}${chunkPath
     .split("/")
     .map((p) => encodeURIComponent(p))
-    .join("/");
+    .join("/")}`;
 }
 
 /**