feat: store location coordinates in createRequest API payload instead…

[rudra-sai-nag-aleti]

Changes

• 'HelpRequestForm.jsx' — Added 'locationCoordinates' state. When geolocation
  succeeds, stores { latitude, longitude } alongside the display address
• 'usePlacesSearchBox.jsx' — Updated 'handleSelectSuggestion' to accept full
  suggestion object and extract coordinates (lat, lon) from OpenStreetMap response
• 'mapHelpRequestPayload.js' — 'requestLocation' now sends
  '{ latitude, longitude }' when coordinates are available, falls back to
  address string if not

Behavior

• UI still shows human-readable address to the user — no change
• API payload sends coordinates instead of address string for DB storage
• Fallback to address string if coordinates are unavailable

Tests

• Updated 'usePlacesSearchBox.test.jsx' — updated suggestion selection test
  to pass full suggestion object with coordinates
• Updated 'mapHelpRequestPayload.test.js' — added test for coordinates payload,
  updated existing location test
• Added 2 new tests to 'HelpRequestForm.test.jsx' — verifies coordinates stored
  when geolocation succeeds

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

Files with missing lines	Coverage Δ
src/pages/HelpRequest/HelpRequestForm.jsx	72.17% <100.00%> (+0.15%)	⬆️
.../pages/HelpRequest/location/usePlacesSearchBox.jsx	100.00% <100.00%> (ø)
src/utils/mapHelpRequestPayload.js	100.00% <100.00%> (ø)

... and 8 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.