fix: don't escape base path in ecmascript runtime to allow for URLs (#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
https://github.com/vercel/next.js/pull/61090
Closes PACK-2282