Enhance README with troubleshooting and FAQ

[Dippp10-ally]

Pull Request

Summary

Issue / Ticket

Closes #632

What does this PR do?

This PR enhances the project documentation by adding comprehensive Troubleshooting and FAQ sections to the README. These additions help users resolve common issues independently and improve the overall onboarding and developer experience.

Changes

• Added a Troubleshooting section covering common installation, configuration, and runtime issues with suggested resolutions.
• Added a Frequently Asked Questions (FAQ) section addressing common user and contributor queries.
• Improved README organization and navigation for easier access to support information.

---

Testing & Verification

How to test

• Local testing: Review the README in GitHub and Markdown preview to ensure all headings, formatting, links, and code blocks render correctly.
• Build / Lint: Not applicable (documentation-only change).
• Responsive checks: Verified readability on Mobile, Tablet, and Desktop.
• Accessibility checks: Confirmed semantic heading hierarchy, readable formatting, and keyboard-accessible Markdown content.

Results

• README renders correctly across supported Markdown viewers.
• Troubleshooting and FAQ sections are properly formatted and easy to navigate.
• No code or application functionality was modified.

---

Screenshots / Screencast (if applicable)

• Before: README did not include Troubleshooting or FAQ sections.
• After: README includes dedicated Troubleshooting and FAQ sections with organized guidance for users and contributors.

---

Release Notes

Added Troubleshooting and FAQ sections to the README to improve documentation and help users resolve common issues more easily.

---

Checklist

• I followed the project's code style guidelines.
• I performed a self-review of my own changes.
• My changes do not introduce new warnings or console errors.
• I verified responsiveness and accessibility requirements.
• I included no unrelated modifications.

[vercel]

@Dippp10-ally is attempting to deploy a commit to the Zuhani's projects Team on Vercel.

A member of the Team first needs to authorize it.

[Dippp10-ally]

@Suhani1234-5 ji , do assign labels called as gssoc:approved, level:intermediate, type:docs , quality:exceptional to above pull request number 633 also.....do merge above pull request number 633 also....