docs: clarify local backend frontend startup order

[KishikaSingh]

Summary

Implements the documentation improvements proposed in the related issue by adding clear guidance for starting the backend and frontend in the correct order during local development.

Changes

• Added a dedicated section explaining the local backend/frontend startup order.
• Included copy-pasteable commands for running both services locally.
• Linked the documentation from the README to improve discoverability.

Why

This improves the onboarding experience for new contributors and helps prevent common setup issues, reducing repeated review questions and confusion during local development.

Testing

• Verified that the documented commands successfully start both the backend and frontend.
• Confirmed the startup sequence works as expected and the frontend connects to the backend.

Checklist

• Documentation section added.
• README updated with a link to the new documentation.
• Commands are copy-pasteable.
• No unrelated code or refactoring included.

Closes #1594

[vercel]

@KishikaSingh is attempting to deploy a commit to the CodeBlooded's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

Hi @KishikaSingh, thanks for contributing to Nyay Setu! 🎉

I have automatically:

• 👤 Assigned this PR to you.
• 🏷️ Applied the gssoc:approved label.

Our workflows will now analyze your changes to classify:

• 📈 PR Difficulty: level:*
• 🧩 PR Type: type:*
• 🌟 PR Quality: quality:*

Tip

Ensure your PR description references the issue it resolves (e.g. Closes #123). This allows the bot to inherit any additional labels from that issue!

Happy coding! 🚀