Mark tsconfig files as JSONC for linguist

[sirreal]

This will help GitHub's syntax highlighting to correctly display
comments in tsconfig files.

For example, note the "invalid" (red) syntax highlighting here:

wordpress-playground/packages/playground/client/tsconfig.lib.json

Lines 14 to 20 in ecff239

	"src/**/*.spec.ts",
	"src/**/*.test.ts",
	// Avoid generating types for this file during the build.
	// The module is not included in bundled build output,
	// so its type definition should be excluded as well.
	"src/additional-remote-origins.ts"
	]

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Marks tsconfig*.json files as JSON-with-Comments for GitHub Linguist so GitHub renders comments correctly (no “invalid JSON” highlighting) in tsconfig files.

Changes:

• Add a .gitattributes rule to classify tsconfig*.json as JSON-with-Comments for Linguist.

---

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

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Updates Git attributes so GitHub Linguist treats tsconfig files as JSON-with-comments, improving syntax highlighting for commented tsconfig*.json files.

Changes:

• Add Linguist language overrides for tsconfig.json and tsconfig.*.json via .gitattributes.

---

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

[sirreal]

I think the language name is already correct with the -.