chore: Add .editorconfig for consistent coding styles

[Ashvin-KS]

Description

Add a .editorconfig file to enforce consistent formatting across all contributors regardless of their editor or IDE.

Problem Statement

With a full-stack project (React frontend + Node.js backend), contributors using different editors may introduce inconsistent indentation, trailing whitespace, and line endings — creating noisy diffs and slowing down reviews.

Proposed Solution

Create a .editorconfig at the project root:

• root = true
• UTF-8 encoding, LF line endings
• 2-space indent for JS/TS/JSX/TSX, JSON, YAML, Markdown, CSS, HTML
• Trim trailing whitespace, insert final newline
• Markdown preserves trailing whitespace (intentional line breaks)

Acceptance Criteria

• .editorconfig exists at project root
• Covers frontend and backend file types
• No changes to existing source files

GSSoC

• I am a registered GSSoC 2026 contributor
• I would like to implement this feature myself

[Copilot]

Pull request overview

Note

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

Adds an .editorconfig to standardize formatting rules across the repo and editors.

Changes:

• Introduces global whitespace/indentation defaults (UTF-8, LF, trim trailing whitespace, 2-space indentation)
• Adds per-file overrides for Markdown (keep trailing whitespace) and Makefile (tabs)

---

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