[WIP] Update ESLint configuration for test files

[Copilot]

Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.

Original prompt

Update ESLint or Next.js configuration to allow the following rules specifically for .test. files so Vercel build passes, without any other code or business logic changes:

• @typescript-eslint/no-explicit-any
• @typescript-eslint/ban-ts-comment (allow @ts-ignore vs @ts-expect-error)
• @typescript-eslint/no-unused-vars
• @next/next/no-img-element
• jsx-a11y/alt-text
• @typescript-eslint/no-unsafe-function-type

Scope:

• Apply exceptions only to test files (filenames containing .test.)
• Keep all other linting behavior unchanged
• No changes beyond config updates needed to unblock build

This pull request was created from Copilot chat.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
bloomstudio	Error		Jan 19, 2026 1:24pm