⚡ Bolt: optimize naver marker memory usage and gc pressure

[ClarusIubar]

💡 What: Refactored useNaverTourismMarkers to eliminate intermediate array allocations (.map, .filter, array spreads). Replaced declarative chaining with standard for...of loops, string concatenation for state signatures, and direct mutations to operations arrays. Added optimization comments.
🎯 Why: Frequent user interactions like map panning cause rapid re-evaluations of visible tourism markers. Previous map/filter/spread chains caused O(N) array allocations per frame, leading to heavy GC pressure and map stutter.
📊 Impact: Eliminates multiple O(N) intermediate array instantiations on every viewport sync tick, directly reducing GC overhead and preserving a smooth 60fps frame budget during heavy map interactions.
🔬 Measurement: Verified that tests pass via npm run test:all. You can measure improvement using the Chrome Performance Profiler on the frontend map page while aggressively panning.

---

PR created automatically by Jules for task 1723989980445648275 started by @ClarusIubar

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.