fix: MapBlock now expects pre-prepared data layers

[dzole0311]

This PR updates the EnhancedMapBlock in next-veda-ui to align with recent veda-ui changes (#1808
). Instead of passing full datasets into MapBlock we now reconcile and prepare baseDataLayer (and optional compareDataLayer) before rendering.

1. MapBlock receives only baseDataLayer and compareDataLayer props
2. No direct passing of raw datasets in MapBlock / aligns the Next.js instance usage with the latest MapBlock changes in veda-ui
3. Fix yarn.lock

Test instructions:

1. Open any story with MapBlock and verify that they work as expected (example)

[netlify]

✅ Deploy Preview for veda-ui-next-test ready!

Name	Link
🔨 Latest commit	df7559d
🔍 Latest deploy log	https://app.netlify.com/projects/veda-ui-next-test/deploys/68b6e6350a9d5f0008eedec7
😎 Deploy Preview	https://deploy-preview-94--veda-ui-next-test.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[vgeorge]

@dzole0311 this is functional, but I wonder if we can avoid disabling type checks. The motivation seems to be that the Veda UI library doesn’t export the type definitions used here, but I think we should copy them into this repo to stay on the type safe side. I know this could bring maintainability issues, but we can create a ticket upstream to increase the exported types coverage.

[dzole0311]

@vgeorge I think we can’t copy the full type set because some of the types use enums and TS is stricter with enums. If you declare the same enum in two places, TS won’t let you use one where the other is expected (eg. you would get an error like Type 'TimeDensity' is not assignable to type '_TimeDensity1').

I made a minimal local copy of the two needed types + linked a tracking issue and removed the ts-nocheck comments.

[vgeorge]

@dzole0311 thanks for opening the upstream ticket. This looks good to merge 🙂