This restriction has been added through this commit after digging in the source code for a bit: https://github.com/vercel/next.js/pull/65821

https://github.com/vercel/next.js/blob/720fe3577eb58050966a44bc1fa88e01fcac3962/packages/next/src/server/image-optimizer.ts#L568

The only way to bypass this restriction currently is by using another image optimisation service or don't optimise the image at all. You can achieve it by not using next/Image or pass an custom image loader file in next.config.ts

loader: 'custom',
loaderFile: './image-loader.ts',

docs: https://nextjs.org/docs/app/api-reference/next-config-js/images

I have created a discussion in next repo: https://github.com/vercel/next.js/discussions/72951