chore: add root .prettierrc and .prettierignore configuration

[zeroknowledge0x]

Summary

Adds root-level Prettier configuration for consistent code formatting across the project.

Changes

• .prettierrc: Root-level Prettier config matching existing Frontend settings
  • Single quotes, trailing commas, 100 char line width
  • Consistent with existing Frontend/.prettierrc
• .prettierignore: Excludes unnecessary files from formatting
  • node_modules, build output, Python files, IDE configs
  • MobileApp directory excluded (has its own config)

Benefits

• Consistent code style across all contributors
• Easier code reviews with standardized formatting
• Can be integrated with pre-commit hooks or CI/CD
• Works with any editor that supports Prettier

Closes #225

[vercel]

@zeroknowledge0x is attempting to deploy a commit to the ritesh Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Warning

Review limit reached

@unsiqasik, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 23 minutes and 3 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 9bb74d44-b8ea-4b3e-9a1b-39015b1b4d2c

📥 Commits

Reviewing files that changed from the base of the PR and between fb6a950 and 9f8c841.

📒 Files selected for processing (2)

• .prettierignore
• .prettierrc

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
29368972	Triggered	Supabase Service Role JWT	b460068	scratch/test_companies.js	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[ritesh-1918]

Hi @unsiqasik! Thanks for the contribution. I have successfully converted your PR's target branch to gssoc to keep our codebase unified.

PR approved and merged! Welcome to the family! 🚀💻

---

🌟 Developer Action Network

Before starting or submitting updates, please complete these quick onboarding steps:

1. ⭐ Star this repository: https://github.com/ritesh-1918/HELPDESK.AI
2. 👤 Follow the Project Admin: https://github.com/ritesh-1918
3. 💼 Connect on LinkedIn: https://www.linkedin.com/in/ritesh1908/

Note: All PR branches must target the gssoc branch, NOT main.