[Engineering]: Break down the monolithic Map into independent and reusable components

Hi,

I spent a few minutes reading the code of the Map component and noticed that it wraps all child components and hooks into a single file, map.tsx.

While this is not a technical issue per se, it becomes a concern from a maintainability perspective.

In addition, AI-assisted tools tend to follow existing patterns, which may lead to even more logic and components being added to the same file over time.

Refactoring the Map into smaller, independent, and reusable components would improve separation of concerns, make the codebase easier to reason about, and reduce the risk of the component becoming increasingly monolithic.

This would also make future changes and extensions safer and more predictable.

Let me know what you think — happy to help with the refactor if we agree on the direction.

Thanks.