fix: ensure MapContainer receives forwarded ref

[fityannugroho]

Summary

This pull request fixes a regression where the map's forwarded ref was not properly passed through components/Map.tsx, which caused downstream consumers relying on the mapRef to fail (e.g. fly-to/bounds operations and map resize handler).

What I changed

• Ensure the MapContainer receives the forwarded ref so external code can access the Leaflet map instance reliably.
• Small defensive change so map initialization is more robust during client hydration.

Root cause

• The regression was introduced by changes in PR Upgrade deps (React 19, etc.) and refactoring #59 which modified component initialization/prop handling and indirectly surfaced the missing ref forwarding in components/Map.tsx. This PR corrects that by forwarding the ref to MapContainer.