fix(earthwidget): Filament KMP 0.7.10, no stale 3D widgets nor shader compile per tab on Windows

[kdroidFilter]

Problem (Windows only)

• 1-2 s latency on every tab open: each new Home compiles its 3D widgets' shaders again. On ANGLE that means HLSL translation plus D3DCompiler, which blocks the UI thread in renderStandaloneView for ~80 ms on the first render of each view, then ~170 ms once the models are loaded.
• Rendering errors: the window kept showing the first content of one of the two D3D11 textures shared with Filament. A readback showed Filament renders the Earth into both textures, yet the widget could show the Earth missing, a stale frame, or garbage. The cause is a legacy shared texture without a keyed mutex: nothing synchronizes Filament's device with the window's.

Both only show up in the native build (ANGLE). Under ./gradlew run, Filament fails to create its engine on ANGLE (Can't get OpenGL version) and falls back to Vulkan. That is a separate issue, not addressed here.

Fix: Filament KMP 0.7.10

• The shared textures carry a keyed mutex (D3D11_RESOURCE_MISC_SHARED_KEYEDMUTEX), held while Filament renders into them. Nucleus already detects this mode and copies each frame out under the mutex, so Nucleus needs no change.
• A process-wide cache of program binaries through Filament's blob cache (Platform::setBlobFunc), capped at 32 MB. A rebuilt material (a new tab) loads its programs from it instead of compiling them again.

Verification (native build, RTX 5060 Ti, new tabopen scenario)

	before	after
UI-thread stall from Filament per new tab	~80 + ~170 ms per view, on every tab	none after the first tab (only the very first Home still compiles)
Earth after an open	visible at 800 ms, then gone at 1500 ms / 2500 ms	visible from 400 ms and stays

New e2e scenario: ZAYIT_E2E_SCENARIO=tabopen (with ZAYIT_E2E_QUICK=1).

Before merging

• Filament KMP 0.7.10 available on Maven Central (publish in progress)