feat: add SVG support to image preloading

[draggie]

Closes #132.

Summary

Adds MVP SVG support to image preloading on iOS and Android by rasterizing SVG input into PNG data before storing it in the existing preloaded image cache.

• Adds inline SVG preload input via svg, width, and height
• Detects remote SVG responses in the existing URL preload path
• Rasterizes SVGs with WebKit on iOS and AndroidSVG on Android
• Keeps widgets using the existing Voltra.Image / preloaded asset rendering path
• Updates iOS and Android examples with SVG widget test controls
• Updates public docs and package types
• Adds Android unit coverage for inline SVG preloading

Validation

• git diff --check
• npm run format:check
• npm run typecheck --workspace voltra
• npm run typecheck --workspace @use-voltra/ios
• npm run typecheck --workspace @use-voltra/android
• npm run test:kotlin --workspace voltra
• Manual iOS example app widget test
• Manual Android example app widget test

Notes

The iOS implementation uses WebKit for runtime SVG rasterization, so the podspec now links WebKit. SVG inputs require explicit positive width and height for predictable raster output.

Preview

iOS

Android

[V3RON]

Good work! I have a couple of ideas for improving code structure.

1. Split URL and SVG preload paths
   The current preload implementation mixes two different concerns in the same native function: downloading from URL and processing inline SVGs. This makes the control flow harder to follow and maintain.
   Recommendation:
   Keep one public JS API, but split native handling into separate URL and SVG-specific functions. JS can dispatch internally so the user still sees a single preloadImages(...) API.

2. Preserve the current JS ergonomics
   There is no need to expose two APIs publicly. The public API can remain a single function, with the JS layer choosing the proper native path based on whether an item contains url or svg.

3. Extract Android image cache/storage responsibilities
   On Android, storage concerns are mixed into VoltraImageManager. The class currently handles:

• fetching/downloading
• SVG detection/rasterization
• cache directory lifecycle
• file writes
• URI generation
• SharedPreferences index management
• stale file cleanup