refactor: abstract community reports localStorage access

[Suprita736]

Pull Request

Description

Extracts the LocationMap component's direct localStorage access for community reports into a new useCommunityReports hook, so the component no longer owns that side effect directly and the hook's return value can be mocked in tests.

Related Issue

Closes #626

Type of Change

• Refactoring

Changes Made

• Added src/hooks/useCommunityReports.js, encapsulating the localStorage read, COMMUNITY_REPORT_SUBMITTED event subscription, and cross-tab storage event sync previously inline in LocationMap.jsx.
• LocationMap.jsx now consumes useCommunityReports() instead of managing its own state/effect for community reports; storage key constant, reader function, and the associated useEffect were removed from the component.

Testing

• Tested locally
• No console errors
• Existing functionality works as expected

Checklist

• My code follows the project guidelines.
• I have tested my changes.
• I have updated the documentation if required.
• My changes address the related issue.
• This PR focuses on a single issue.

Additional Notes

Symptom reports still read localStorage inline in LocationMap.jsx — left untouched since #626 scopes only community reports. Could be a good follow-up issue (useSymptomReports) if desired.

[vercel]

@Suprita736 is attempting to deploy a commit to the Aditya Mahajan's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

Thank You for Your Contribution! 🎉

Hi @Suprita736,

Thank you for opening this Pull Request and contributing to our project. We truly appreciate your efforts.

Please make sure that:

• Your code follows the project's guidelines.
• You have linked the appropriate issue (if applicable).
• Screenshots are added for UI/UX changes.
• Your PR is ready for review.

The maintainer @Aditya8369 will review your PR shortly!

Happy Contributing! 🚀

[github-actions]

🎉 Your PR just got merged, @Suprita736 — thank you for contributing to Pollution Control Hub!

Your work is now part of the project. Here's what to do next:

• ⭐ If you haven't already, consider giving the repo a star — it helps us grow.
• 📢 Share your contribution on LinkedIn, Twitter, or wherever you hang out. You shipped open source!
• 🔍 Browse other open issues if you want to keep contributing.

We really appreciate you taking the time. See you in the next PR! 🚀