chore: prettier-ignore tsconfig.json so next build reformatting doesn't fail check-format (#4885)

[frano-m]

Summary

Closes #4885.

next build / next dev rewrites tsconfig.json into a multiline shape (expanded arrays + a .next/dev/types/**/*.ts include entry) that fails prettier --check. Because the pre-commit hook runs check-format (prettier --check .) across the whole repo, committing after a build fails the hook on tsconfig.json — forcing a --no-verify bypass — and the file shows as perpetually "modified" in git status.

tsconfig.json is a Next-managed file, so this adds it to .prettierignore, letting Next own its format without prettier fighting it. The committed tsconfig.json itself is already prettier-clean and is left unchanged.

Change

• .prettierignore: add tsconfig.json under the existing # next.js section.

Verification

• With tsconfig.json in its build-modified (multiline) state, npm run check-format now exits 0 (previously failed)
• Committed tsconfig.json unchanged and still prettier-clean
• Pre-commit hook (check-format + lint + tsc) passes without --no-verify

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR prevents next build / next dev from causing Prettier format-check failures by excluding the Next-managed tsconfig.json from repository-wide prettier --check runs, aligning with the workflow where Next may rewrite that file into a shape Prettier rejects.

Changes:

• Add tsconfig.json to .prettierignore under the existing Next.js ignore section.
• Document why it’s ignored (Next rewrites it during build; reference #4885).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.