Including exclamation mark(" ! ") in assetPrefix compilation will result in an error

Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/xenodochial-easley-ddh8vq?workspaceId=6bdce0be-af7a-405b-adec-ac633e9ed70d

To Reproduce

Add the following config to "next.config.mjs":

output: "export",
assetPrefix: "https://mycdn.com/!mark",

if the assetPrefix incude "!" will trigger error
if change the "!" to "21%" will be ok (but not my need)

Current vs. Expected behavior

Current:

➜  workspace git:(master) ✗ yarn build
yarn run v1.22.19
$ next build
  ▲ Next.js 15.0.0-canary.196

   Creating an optimized production build ...
Failed to compile.

Module not found: Error: Can't resolve 'mark&nextConfigOutput=export&flyingShuttle=false&nextConfigExperimentalUseEarlyImport=&preferredRegion=&middlewareConfig=e30%3D' in '/project/workspace'

Module not found: Error: Can't resolve 'mark&nextConfigOutput=export&flyingShuttle=false&nextConfigExperimentalUseEarlyImport=&preferredRegion=&middlewareConfig=e30%3D' in '/project/workspace'

Module not found: Error: Can't resolve 'mark&nextConfigOutput=export&flyingShuttle=false&nextConfigExperimentalUseEarlyImport=&preferredRegion=&middlewareConfig=e30%3D' in '/project/workspace'


> Build failed because of webpack errors
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
  Available memory (MB): 4102
  Available CPU cores: 2
Binaries:
  Node: 20.9.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.10.2
Relevant Packages:
  next: 15.0.0-canary.196 // Latest available version is detected (15.0.0-canary.196).
  eslint-config-next: N/A
  react: 19.0.0-rc-77b637d6-20241016
  react-dom: 19.0.0-rc-77b637d6-20241016
  typescript: 5.3.3
Next.js Config:
  output: export

Which area(s) are affected? (Select all that apply)

create-next-app

Which stage(s) are affected? (Select all that apply)

next build (local)

Additional context

Both 15.0 and 14.x is not ok

Reproduce the failure with the assetPrefix in next.config.mjs and run next build using the linked CodeSandbox setup. Compare it with the working percent-encoded value, then trace how the assetPrefix is handled during the build; done means an exclamation mark no longer produces the reported module-resolution error.