feat: Add pre-commit configuration for markdown files

[MUFFANUJ]

What this PR does:
This PR introduces an optional pre-commit configuration to help maintain Markdown file hygiene. It adds a
.pre-commit-config.yaml file with the following hooks, configured to run only on Markdown (.md) files:

• trailing-whitespace: Trims trailing whitespace.
• end-of-file-fixer: Ensures files end with a newline.
• check-merge-conflict: Prevents committing unresolved merge conflicts.
• codespell: Checks for common spelling errors.
  Why we need it:

Which issue(s) this PR fixes:

• To provide quick, local feedback to contributors on common formatting issues (whitespace, EOF) without waiting for CI.
• To catch merge conflict markers before they are accidentally committed.
• To help catch spelling errors in documentation.
• To improve the overall quality of documentation contributions with minimal friction.

Fixes #6424

Visuals:

Screen.Recording.2026-01-27.at.1.19.13.PM.mov

Does this PR introduce a user-facing change?:

• How are users affected by this change: Contributors can optionally use pre-commit hooks to automatically lint their Markdown changes locally.
• Is this breaking change: NO
• How to migrate (if breaking change): N/A

[eeshaanSA]

Hi, we discussed this in the community meeting. Sounds like a good idea. Though, we are not sure of the scope of the pre-commit hooks. It is best to only limit it to v1 docs, and not the other versions. Additionally, it might just be better if we add a CI for this instead of an optional pre-commit hook, because most contributors would ignore it anyway.

[Ayushmore1214]

Looks good

[github-actions]

This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions]

This PR was closed because it has been stalled for 7 days with no activity. Feel free to reopen if still applicable.