Avoid over-optimization of Notion/AWS S3 images (or any image where the url changes across time)

[Vadorequest]

Describe the feature you'd like to request

I use a Vercel hobby account and ran into an unexpected images optimization rate limit warning.

See transitive-bullshit/nextjs-notion-starter-kit#279

I replied to the Vercel support team about the issue.

I'm looking for a smart solution, I don't believe there is a way to make Next.js understand that the image "X" that was optimized before is the same as the image "Y", since it relies on the URL to resolve whether the image is new or not.

Here is an example of the image that is used by Notion.

Describe the solution you'd like

I wonder if this pattern might be common-enough for Next.js to handle it gracefully, or if it's something too specific to a particular provider (Notion) to be handled by the framework.

Or, if that use-case of "an image for which the url changes over time" is widely-enough used to provide an alternative way to make the Next.js framework understand that it was optimized before and shouldn't be optimized again.

Describe alternatives you've considered

Disable Next.js image optimizations 😢