Redundant `no-img-element` eslint rule when working in `@vercel/og` response jsx (app folder route handler)

### Verify canary release - [X] I verified that the issue exists in the latest Next.js canary release ### Provide environment information ```bash Operating System: Platform: win32 Arch: x64 Version: Windows 10 Pro Binaries: Node: 18.13.0 npm: N/A Yarn: N/A pnpm: N/A Relevant packages: next: 13.2.5-canary.2 eslint-config-next: 13.2.5-canary.2 react: 18.2.0 react-dom: 18.2.0 ``` ### Which area(s) of Next.js are affected? (leave empty if unsure) _No response_ ### Link to the code that reproduces this issue https://github.com/Arctomachine/next-og-img-eslint-warning ### To Reproduce 1. `pnpm install`, warning might appear in your IDE already 2. `pnpm build`, look at console warnings ### Describe the Bug When using route handler (app folder) to generate image with `@vercel/og`, `next/image` components and their benefits are not relevant here, it is not even working here. So using normal `<img />` tag is perfectly valid in this scenario. But eslint gives this warning > Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element ### Expected Behavior Disable `no-img-element` rule when working inside `@vercel/og` response jsx. ### Which browser are you using? (if relevant) _No response_ ### How are you deploying your application? (if relevant) _No response_